Jump to content
Sign in to follow this  
t-zwck

could not start remote installation service on local computer

Recommended Posts

For those of you that don't know Service Pack 2 is now available (on windows update and as a separate download) for Windows 2003 Server.

 

Hidden Content

    Give reaction to this post to see the hidden content.

 

Some people may inadvertently upgrade their Windows 2003 sp1 servers to sp2 without reading the relase notes, and if that server was a RIS server (remote installation services via pxe boot) then you may be in for a surprise.

 

Amonsgt other things (release notes) Service pack 2 upgrades your RIS server to act as a Windows Deployment Service, however in the process of doing so it effectively renders the 'old' Remote installation SERVICE obsolete (and this explains the cryptic errors below).

 

 

 

What does this mean ?

 

If they didn't know about it what they will see is all PXE boot attempts to their 'RIS' server will FAIL.

 

 

Symptoms include:-

 

Error on startup of the server immediately (and after every reboot) after installing Service Pack 2, stating

 

'a service failed to start, please check the event viewer for details'.

 

PXE boot failure on the client (no boot filename received error).

 

RIS service on the server fails to start with the following error if you try to start it manually -

 

'Could not start Remote Installation Service on local computer.

Error 127: the specified procedure could not be found.'

 

 

Steps to alleviate the problem:-

 

Advise customers to open administrative tools and to click on 'services'. Scroll down to 'Windows Deployment Services server' service, it will NOT be started and it's state is set to 'manual'. Ask the customer to start the service (they may wish to set it's startup type to 'automatic'.

 

Now, the customer should be able to PXE boot their clients as normal to the RIS server and deploy images exactly as they did before.

 

Other things to note:-

 

The new service is actually very useful to your customer, because now they can deploy Vista images via this server, however as SP2 is forcing the change gently from RIS to Windows Deployment Services what you will see are three modes for the new service (shown below). So effectively if the customer upgrades a SP1 RIS server to SP2, then they will be able to use the Windows Deployment Services in legacy mode to retain compatability with RIS.

 

More info about this below:-

 

Windows Deployment Services

 

Starting with this version of Windows Server 2003 with SP2, Remote Installation Services is replaced by Windows Deployment Services. You can use Windows Deployment Services to set up new computers through a network-based installation without having to be physically present at each computer and without having to install directly from DVD media. For more information about Windows Deployment Services, see the Windows Deployment Services Update Step-by-Step Guide

 

Overview on technet >

Hidden Content

    Give reaction to this post to see the hidden content.

 

Initial server mode

The method of installation and subsequent configuration actions dictate the initial server mode as follows:

Task Procedure

To get to Legacy mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.

2. Install the Windows Deployment Services update.

3. Run RISETUP and add an image.

To get to Mixed mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.

2. Run RISETUP and add an image.

3. Install the Windows Deployment Services update.

4. Run WDSUTIL /initialize-server.

To get to Native mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.

2. Install the Windows Deployment Services update.

3. Run WDSUTIL /initialize-server.

 

here's an example of that

 

Hidden Content

    Give reaction to this post to see the hidden content.

 

the /verbose command is very useful for seeing errors (such as access denied). I did receive access denied errors when running the Windows Deployment Services GUI wizard, and after much searching It turned out to be possibly related to

 

1. I had renamed my RemoteInstall folder to Remoteinstall2k3 (easy to rename back, but then you must re-share it to REMINST and then re-scan the domain controller in Active Directory users and computers, select the domain, choose properties, choose Remote install, choose verify, it will find errors and correct them.

 

2. verify your permissions on the REMINST share, if they are read-only for EVERYONE then WDS will fail with 'access denied'.

 

Hidden Content

    Give reaction to this post to see the hidden content.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...