Major issue with Rapid Deployment Pack 2.20? HELP!!!

[mjcb2000]

Major Issue with 6.5 - Help!!!


--------------------------------------------------------------------------------

Hello,

I have just found that when I have a machine with IIS 6 installed (Windows 2003) then create an image of the machine using RDP 6.5, after the image is completed, the IIS_WPG group and the Machine\IUSR accounts are reset. After the image is taken, I look at the properties of the c:\inetpub\wwwroot directory and it shows 2 SIDs rather than the accounts (see screenshot). I can re-create this issue on any different server and using RDP. This is causing huge issues with some of our production servers with IIS 6.

Has anyone else experienced this? If so, is there a solution to it?

Thanks,

[Doug Swain]

IIS like SQL does not image well because of various issues such as the one you noticed. I would only image IIS and SQL for disaster recovery images.

[mjcb2000]

The only time we image is if we need to backout a change, or for disaster recovery. This issue would not allow us to use the Rapid Imaging utility. We would be forced to use Ghost as it doesn't mess around with the domain accounts.

[James Sedano]

man i had enough with RDP.. it works as long as you use sidgen, but beware that Microsoft will not support you unless you use sysprep.. this is usually done for image distribution.. now for OS Cloning RDP is not the tool to use, it causes problems since it's hard to stop the Aclient from reconfiguring your machine.. if you want to clone your server use something like GHOST.. it'll not change your SID unless you want it to.. good luck..

[mjcb2000]

Ya it's crazy. I am working around this by just running a script to start the RDEPLOY. I then manually click around to image the machine.

I am going to try creating a WINPE boot enviornment in RDP to see if I get the same issues. Altiris have tried to replicate this through WinPE, but they can't. I am not sure why they wouldn't test it using DOS.