Jump to content

RIS/WDS issue when upgrading to SP2


Recommended Posts

All our Windows 2003 Standard Edt SP1 servers with RIS installed are showing an error when updated to SP2. With pre-SP2 machines, RIS is a native Windows component (BINLSVC service), with SP2 RIS is replaced with WDS (WDSServer service). Once we upgrade a machine from running the SP1 level & BINLSVC Service to SP2, we expect that the BINLSVC service is replaced

by the WDSServer service upon reboot/installation. We would also expect that the "new" service is set to automatically start once the machine boots, and that the old service is removed. When we perform this upgrade, the machine displays and error when it reboots from the SP2 install:

"At least one driver fail to start during startup." Checking the Event Viewer, the following entry can be found in the System logg:

Source: Service Control Manager

Event ID: 7023

Type: Error

"The Remote Installation service terminated with the following error:

The specified procedure could not be found.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

Checking the service console, both the BINLSVC and the WDSServer is present at the same time. The BINLSVC is set to Automatic startup type, while the WDSServer is set to Manual startup.

None of the services are running on the systems that we have tried this on so far, so once we migrate systems to SP2, we loose the PXE functionality. Totally removing the RIS/WDS components,

rebooting the systems, then adding the WDS component from a SP2 level will not show the same issue, even if adding an image using risetup /add on the SP2 level system. However, this is not an acceptable solution for us. Anyone seen or know this one?

Link to comment
Share on other sites


One question - have you modified the permissions that affect the REMINST folder? I've seen this in beta testing when the "Authenticated Users" group was removed from the NTFS permissions on the share - for whatever reason, when these permissions didn't apply to the REMINST share when SP2 was applied, the BINLSVC service wasn't removed, and the WDS service was set to manual (and all other sorts of service issues ensued even after the binlsvc was removed manually). If we restored the same image to the box but set the permissions to what they were default after the RIS installation, everything worked just fine. Same box, just different permissions on the REMINST folder, and different behavior entirely during the SP2 install.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...