bakkee

Allright, favor towards unattended setup in stead of using images is growing by the moment... Thanks.

Nobody any suggestions on a Detachedprogram equivalent in sysprep ?

Isn't the kickoff of minisetup not 'just' a special sort of shell replacement in the registry ? I should focus on the issue why this is not beiing removed... Is there something wrong with the registry in the image (corrupt or something) ? Perhaps someone is able to give some suggestions on logfiles in this stadium. Are you able to mount the 'image' registry in regedit ? Succes !

Hi, I was wondering, is there an alternative to the detachedprogram option in the unattend.txt / winnt.sif file, available for use in sysprep.inf ? I've done some testing but can't seem to get it working. This might not be a surprise, as I can't find any mentioning of this beïng used. Any help would be appreciated. Thanks in advance. Erik Bakker. <edit> deleted some unneeded background info

The only suggestion I can give is that there is another incompatibility besides the MP - UP difference. I know that some manufacturers use custom hal.dll files for their pc's. I suggest you compare the hal from the uniprocessor pc to the hal, that is provided via the hal.inf in the sysprep setup. Besides, this approach (building an image on a dualcore pc, and deploying it on a uniprocessor pc) isn't the most 'riskavoiding' if I may suggest. A uniprocessor installation will work on a dual processor pc (with degraded performance, that is..) but most buisiness applications don't even notice the second processor. It's just like building an sysprep image on a SCSI system, for deployment on IDE based systems. It _can_ be done, but it's not the easy road.. We always use the same reference pc (in our case : a laptop) to (re)build the image, to avoid incompatibities when redeploying a new version of the same image to a pc with an older version of that image. If that image needs adaptation, then the adaptations are made on the basis of that particular image. My suggestion is, keep on building the image on a uniprocessor pc, and adapt that image for use on a multicore pc, not the other way 'round. Good luck.

Hi, my full name is Erik Bakker, and I live in Holland. I work for an ICT organisation that manages about 16000 pc's, about 1200 servers, at roughly 80+ locations all over the country. Currently we use Windows 2000 on about 70 different types of hardwareplatforms (laptops and desktops) , witch all are obtained from the top 2 PC selling companies. OS deployment for the workstations is done by means of Altiris, and all those configurations are served with only 1 sysprepped image. OS Deployment for the servers is done by unattended setup, but managed from HP RDP (basically Altiris, but HP-branded). Right now the descision is made to migrate the clients to Windows XP. Server Based Computing will be introduced this year, and all clients will be fitted with Citrix client-software. Right now I'm developing a solution to roll out XP,unattended, using Altiris. I want to build a solution that can be used in a concentrated serverenvironment, and that can be managed centrally. Of cause networkload is to be minimized, and all actions should be unattended. I visited this forum a couple of times, to find lots of interesting stuff. I hope to learn much from, and contribute a lot to the discussions on OS deployment. Thanks. Erik Bakker Haarlem Holland