harka13

You can take a look at WSUS here (http://www.microsoft.com/windowsserversystem/updateservices/evaluation/default.mspx) I have it running at home and find it quite good for managing a number of machines. You can also set it up to daisy chain to other WSUS servers, so in theory you can roll this system out to the entire organisation and still only have one server that downloads the patches from the Microsoft Site. Very nice - good price too (free) I have been testing it since it was still called WUS - cannot complain - never had one problem with it. Once download - many distributions. Love it!

go here (http://support.microsoft.com/?id=893803) and download the redistributable file from the desktop your having problems with and see if it will install from the download. Also - read this news (http://www.msfn.org/comments.php?shownews=13094)

I have a laptop which is driving me insane. It is running WinXP Sp2 (fresh image) and i am trying to map a drive for the user. Now i can map it ok, but after a day or two it drops off and if you view the mapped drive list using 'net use' it shows the drive as unavailable. However, the same laptop has another mapped drive to the same remote server (different folder though) and its mapping is just fine - never goes unavailable. The laptop definately has access to the remote resource, you can navigate to the remote resource by using the Run command and entering the full UNC path. The window always pops up without an error. You can even create a shortcut on the desktop to the remote resource and it always works - at the same time the mapped network drive will still be unavailable. Try to click on the mapped drive you get the error "... path not found.." (something along these lines)... I am not sure what else to check - any ideas would be great...

not sure if this will help but you can check gpedit.msc, run this and drill down into the folowing location: Windows settings -> Security Settings -> Local Policies -> User Rights, Within here you should see one policy called "Access this computer from the network" - check what has been enabled in this policy.... Good luck - hope this helps.

One way is to use the Alternate Configuration options within the network connection TCP/IP properties windows. This option is available to you if you are using DHCP for your main domains configuration. You can put in the IP address information in the Alternate Configuration tab that works with your workgroup, and leave the General tab set to DHCP. What happens then is that if XP cannot contact your networks DHCP server it will automatically assume the IP configuration that you have specified in the Alernate Configuration tab. So while your in the office (assuming you are using DHCP) you are ok to join the domain, and while your at home (on the workgroup) you can still have the same IP/subnet information to continue to communicate there as well.