Contributed By: Christian Wheelwright
I have been testing out SUS for the last few days and wanted to let people know about some issues/resolutions in case they run into the same problems.

I am using VMware 4.0 to test the client side so that I can try various installs quickly and repeatedly. I got the server up and running and was able to get the client to see the SUS server and download updates from it. The problem was that most updates would fail to install. The windows update.log would referenced the 'IUHIST.XML' file and say:

(Error 0x80070052: The directory or file cannot be created.)

I found references on the newsgroup to people having the same problem with mapped network drives. If the mapped drive was bigger but the user didn't have the needed permissions, the install would fail. After a while I noticed that although I didn't have mapped network drives, VMware 4.0 had created a V: drive called Shared Folders. This is used to share files between virtual machines. I found on some VMware newsgroups that the Shared Folders drive is still a little buggy and has issues with permissions. Of course the V: drive was slightly bigger than the C: drive and so SUS was trying to use it for temporary space. I disabled the Shared Folders and retried the updates and everything ran smoothly. So if you have VMWare 4.0 and want to use SUS, you have to turn of the Shared Folders feature.