Lima's questions

We have had a PDF containing a virus get through our email filter, the anti-virus on the email filter didn't detect the virus however the anti-virus on the desktop did detect the virus and promptly dealt with it.

When de-briefing the user they have reported that they didn't open the attachment, they determined it was spam and when they clicked on the email do delete it the virus was detected.

I haven't been able to determine whether Outlook does download an attachment when you click on it, the user has reading pane enabled.

Can anyone advise if Outlook is downloading attachments on opening an email and whether it can be disabled?

We are not wanting to disable attachments, just making it so that the attachment is only downloaded when the attachment is actually opened by the user.

We are a business of under 200 PC's that are looking at implementing preventative maintenance tasks such as regular imaging or updates but would like to see if there is a better method then IT coming in on a weekend every month to turn on the PC's and do whatever the task is.

We are a MS Server house, we are using WDS to capture and deploy images and use MS DHCP.

Many moons ago I worked at a school that had primarily Unix servers (ISC DHCP) and the guy there built a system where the PC's would boot into PXE and quickly determine whether the PC was earmarked for imaging or if it is meant to boot into Windows. This was a great system, but I had little to do with the maintenance or development and so don't know how it was exactly implemented.

What I was wondering is if there is a way of implementing something like this using MS Servers, DHCP and WDS. We would like to be able to set a flag for a PC to boot into WinPE or to boot from the Hard Disk. I was hoping we could setup a database (MS SQL Server) which could contain the PC MAC Address and a flag for whether the PC boots into Windows (local HDD) or WinPE (PXE Boot)?

We are wanting the PC's to be always set to boot from the NIC first and HDD second so whatever solution we implement the boot time to Windows shouldn't be too much longer then it currently is, as the PC's would be booting to local HDD more often then not we don't want the users waiting for minutes for PXE to time out or WinPE to fully load.

A user is experiencing a problem whereby when sending emails, some emails are being allocated the same Message ID. The issue looks to occur when the user has a draft email and they forward the draft to one person, and then later send the draft to another person.

I have done an email trace in Exchange, searching only on Message ID and Exchange is returning the two emails.

Our environment is Outlook 2010 SP1, Exchange 2010 + Exchange 2007, our users run in Outlook Cache Mode.

I have done some research and from what I have read it is the client which generates the Message ID, is this correct?

Is anyone aware of any known issues with two different emails receiving the same Message ID? Does anyone have any knowledge on how this could occur and what we can do to resolve this?

The latest example email's were sent just over 1 hour apart (1 hour, 1 minute), have the same subject, Message ID, sender, but different recipients and message body (only slightly).

I have a very strange issue that is affecting non-domain admin users. When a standard user within Citrix (Presentation Server 4.0) attempts to print to a local printer (attached via USB to the local computer) the job comes up in the server printer queue straight away as paused.

If the user right-clicks the job in the printer queue and selects Resume the job status changes to Paused - Printing, but doesn't print.

I have been able to narrow down, that if I send a test job from notepad to the printer, the job comes up as Paused but after clicking Resume the print job is then sent to the local computers printer queue.

I then did a test in Word and again the printer job displays as Paused in the Printer queue, however when clicking resume the amount of data sent to the printer is 128KB, and clicking resume again increased to 256KB and continuing this each time the job was resumed until it reached the size of the job and then the job appears in the local printer queue.

The notepad test document was only 9KB and the Word document was 619KB. I have been able to replicate this 128KB data sending with several different test jobs from Word and also the Printer test page. On all occassions it will send 128KB (or the size of the job), and then requires an additional resume to complete the job transmission.

The environment is:

• Local PC: Windows XP Professional SP3 32-bit
• Local Printer: HP LaserJet Professional CP1020
• Server: Windows Server 2003 Standard 32-bit
• Citrix: Citrix Presentation Server 4.0

The printer driver in use in the Citrix environment has been mapped to the Citrix Universal Print Driver, removing this forced maping makes the print driver in use on the Citrix server the HP LaserJet print driver (which has been added to the Server 2003 environment), however this then results in only ~1.3KB (appears to change on each resume) being sent to the printer on each resume.

Edit: The printer name is HPCP1020, as I have read that Citrix has an issue with long names, but this still resulted in the same behaviour.

Does anyone have any ideas or experience of what is occuring and how we could go about resolving this issue or debugging this further?

Thanks,

Matt

I am learning how to manage databases for my company and while I have pretty good understanding of using a database, I can definately see that it is completely different administering a database.

My possition is we are a small team and we previously had no one manageing the database servers, if something went wrong we would fix it but there was no pro-active maintenance.

I am putting together some documentation of best practices that we should be using, fixes to problems discovered, and methods to prevent issues from occuring. At the moment my managers are reluctant to patch the DB Servers (OS and DB Software), which I believe is insanity but they are senior and "know best".

Our environment is Server 2003, with 5 DB Servers, three MSSQL 2005 and two MSSQL2000. The DB servers are all private and do not face the internet. They are behind our firewall. The fact they are not public is the reasoning behind the managers reluctance to patch the servers.

What I would like to know is:

How people manage patching of the SQL Servers and OS? Is it necessary to patch them? List item When do you apply patches (immeadiately, after a couple days to wait for problems to be encountered and documented, other)? List item White papers, technical documentation, good blogs, etc that you can recommend. Any help would be greatly appreciated as I believe that they should be patched to at the least the most recent SP and perhaps the second recent Cummalative Update, but I dont have any form of best practices to base this on so would be most keen to learn what people do.

If you need further information please dont hesitate in contacting me.

Thanks,

Lima