10 May 2005

Automated Deployment Services (ADS) 1.0 and Windows Server 2003 SP1 Gotcha

This seemed a timely reminder with my webcast on Windows Server 2003 SP1 this afternoon. A small gotcha which caught me out last week when installing an ADS controller was that when ADS asks for the Windows Server 2003 media, you must use the RTM version, not a slipstreamed SP1 media. The ADS services won't start otherwise. Ironically, the only thing I didn't have to hand at the time was an RTM install - I've slipstreamed everything. Doh! This gotcha is due to be fixed in the next release of ADS.

 

Filed under: , ,
 

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Jeffery Hicks said:
This bugged me to no end until I figured it out. Although I was getting a corrupt NTFS partition or bad/missing ntfs.sys. ADS ran just fine. I compared file versions of ntfs.sys and realized the SP1 version was probably the culprit.
11 May 05 at 1:27 PM
# daniel barichello said:
Hi, Have you tried to do a image capture since applying SP1. I am having timeout errors now. This never happend prior to sp1.
15 June 05 at 12:38 AM
# jhoward said:
Hi Daniel

Sorry, no. I haven't had a chance to try this out yet. The hardware I've been using at the roadshows were built before SP1 came out, and I left them in this state rather than change anything. Besides, they're actually rented kit, so I don't have them around to be able to investigate further. I'll be using the same kit for TechEd, so won't in reality get a chance to try this out until mid-July (VPCs and VS to try it out is too slow really). However, I'm not aware of any issues with SP1 being applied to the ADS controller box itself, only the issue about using SP1 files within the ADS installation itself.

Is the _only_ thing which has changed is the application of SP1 to the ADS controller? Are you capturing a machine which had been successfully previously been captured? What is the error on the box being captured itself? There are some common causes documented in vsmt.chm such as drivers and hotfixes.

Hope this helps?
Regards,
John.
16 June 05 at 7:31 AM

Leave a Comment

Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.

(required) 
(optional)
(required) 
Page view tracker