andrewpayne

I have used both VMware and VirtualPC - VMWare v5 wins hands down on performance without question and well worth the little extra in price.

I have just tried the following: msiexec /i sav10.msi /qb RUNSCAN=0 RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS on my vmware machine and this does appear to suppress the initial rtvscan process. Can anyone else confirm this on their machines?

Symantec Anti Virus Corporate v9 has ZERO competition...! (Never had any probs with LiveUpdate) However - I DETEST Norton Internet Security with a vengeance - steer well clear! Once on always on (bit like AOL?!)

Start/Run/Regedit HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion \Policies\Explorer. Create a new DWORD value and name it "DisallowRun" set the value to "1" to enable application restrictions or "0" to allow all applications to run. Then create a new sub-key called HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ Policies\Explorer\DisallowRun and define the applications the are to be restricted. Creating a new string value for each application, named as consecutive numbers, and setting the value to the filename to be restricted (e.g. "iexplore.exe" to prevent Internet Explorer). Restart Windows for the changes to take effect.

I was using Firefox 1.0.2 and after 'upgrading' to 1.0.3 and reinstalling my extensions I tried the newly released Opera 8 Final - wow! I am converted to Opera. It's tabbed browsing (on by default - unlike Firefox, which needed an extension to prevent new windows spawning) is second to none; its default theme is smart; and best of all is (again on by default) the Session manager where I can open a related group of pages/tabs at the same time. All without a single 'extension' or add-in. Lightweight, Fast and (so far!) the most secure browser available! Here's for Opera 8! Try it now and see for yourself! Link to MSFN Topic for Opera 8 Final

I agree with the slipstream method for workstations - as a reinstallation of the OS is preferable, however @klasika is completely right - it would be *crazy* to even consider reinstallation of a server's OS whenever a service pack was released. Fine if the server is new and you CAN reinstall the OS (RAID drivers etc considered!) But in the real world you'd expect that service packing Server OS would be a cumulative task - ie existing, then SP1, SP2 etc. as I have for many of my oldest and reliable Windows 2000 Servers who all began service as humble SP1 or Gold versions. However - whenever installing a cumulative SP I would always recommend to my peers to: 1. disable any anti virus and anti spyware apps that may be running 2. disable any software firewalls (why install these in the 1st place??!) Stick to a hardware firewall or even better set up zones within your network between hardware firewalls to protect against both internet (outside) and client (internal) compromises. 3. Install the Service Pack - always keep the uninstall/previous versions if offered (I note that 2003 SP1 you have no option - but you do for Windows 2000 SP4) 4. Test everything is OK - event logs etc 5. Roll out the update to the other servers, if applicable just my penny's worth based on my experience

Yeah - it's been a long day! Thanks for the ico!

@kelsenellenelvian - cheers!

Thanks @kelsenellenelvian could you perhaps upload/link to the actual icon file instead of posting a picture of it? Appreciated

Excellent stuff - BTW could you post a link to the setup icon you use, its real cool! Cheers

@XPero - The best yet! mind you - from the creator of XPize what more could we expect?

Try the following WindowsUpdate recovery procedure: 1. Empty Temporary Internet Files 2. Find C:\WINDOWS\system32\CatRoot and CatRoot2 folders and delete contents (this is the working folder for WindowsUpdate ActiveX interaction) do NOT delete the actual folders themselves reboot PC and try WindowsUpdate again.

Guess a reinstallation of XP is the next option

Did you try the service_boot_start option?

click here for full syntax of the enable command you should be typing enable ntfs service_auto_start to enable the auto start of ntfs service.

I have just recreated another admin install of SAV903 to 'start again' - this time with a Feb 2005 vir def folder - and the symptoms are exactly the same - LU insists on downloading the entire update package regardless. Its almost as though the vir defs folder is either missing something or the date/time stamps are incorrect?

is it me or is anyone else having a major issue with replacing the Virus Defs? If I delete and replace files as above - the installer whines about missing VIRSCANT.DAT as this is the only file missing from the downloaded i32 archive. I then Copy & Paste the extracted files to said folder and install on a fresh VirtualPC and voila - LiveUpdate then insists on all 6.76MB of updates download afterwards. FYI - I am using SAV 9.0.3.1000 with LU26

have you tried disabling this service to see the effects? FYI - Volume Shadow Copying will have an adverse effect if the Volumes you are shadowing are on the same drive controller as the Server OS.

You have a Windows Server 2003 with one hard drive? Is this Hard Drive a SCSI or IDE/SATA? I would recommend you adding another Hard Drive for file sharing - leaving the C/D for Windows Server's own use. I would always recommend a SCSI RAID controller with three 72GB U320 SCSI Hard Drives with a minimum of two containers for all Windows 2003 Servers. BTW - the activity you are getting whilst users are 'deleting' files sounds like the Volume Shadow service is following the deletions to enable users to 'undelete' or retrieve deleted files later on. - more info here

can't beat the Xeon with 2MB Level 2 cache!

here you go - http://support.microsoft.com/kb/231747/EN-US/ B)

I bought a USB caddy for laptop hard drives for exactly that purpose! you can get one for about £5-£10 from ebay here If you can wait a few days - it would be the safest bet to retrieve your files and then perform a clean OS install safe in the knowledge you already have your files

Does your Tosh boot up in Safe Mode?

Cheers IRP Excellent Tool and one that has saved me going back to a pre-integrated I386 that I had saved last year! nice one!

You want to select a domain user during the installation? You will need to modify the Group Policy for your OU in AD to include a startup script to run the above command I mentioned - however insert the name of a group rather than user (eg LOCALADMIN) and add all domain users who require local administrator rights to this group. By default - Domain Users are Power Users not Local Admin - as I know you are aware. I had a similar problem with ensuring control over Local Administrators and the Startup Script appled to Computer using GP in OU was my method of overcoming this. However - Unattended Installations should be automated and require little if any interaction. So personally I would setup the installation using the default Administrator account with auto logon etc - and keep the selection of domain users to become local admins as a 'post installation' - done by Group Policy for your AD. This would be much easier and far more efficient to manage. Just my thoughts...