W2K3 SP2 breaks RIS?

Hello,

After installing SP2 on W2K3R2 we get following error when trying to start
the BINSLV we get this error ...

Any sugestions are welcome!

Thx

---------------------------
Services
---------------------------
Could not start the Remote Installation service on Local Computer. Error
127: The specified procedure could not be found.



Error 127: The specified procedure could not be found.


---------------------------
OK
---------------------------

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 3/16/2007
Time: 1:51:17 PM
User: N/A
Computer: AOCSRV06
Description:
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.

Oeps, it's because of the new Windows Deployment Service that needed to be
initialized ... wdsutil /initialize-Server /reminst:"E:\RemoteInstall"

Cheers

"WorkingHard" <WorkingHard@news.postalias> wrote in message
news:eK3oNe9ZHHA.3996@TK2MSFTNGP03.phx.gbl...
> Hello,
>
> After installing SP2 on W2K3R2 we get following error when trying to start
> the BINSLV we get this error ...
>
> Any sugestions are welcome!
>
> Thx
>
> ---------------------------
> Services
> ---------------------------
> Could not start the Remote Installation service on Local Computer. Error
> 127: The specified procedure could not be found.
>
>
>
> Error 127: The specified procedure could not be found.
>
>
> ---------------------------
> OK
> ---------------------------
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7023
> Date: 3/16/2007
> Time: 1:51:17 PM
> User: N/A
> Computer: AOCSRV06
> Description:
> 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.
>
>

Hi there,

I tried running this command, however I'm still getting the error message. I've used the correct Drive letter, still no go...

Any ideas?


Cheers,
Low_ridEr

the following solution worked for me, and my windows 2003 sp2 server is functioning exactly as before the upgrade

http://www.windows-noob.com/forums/i...p?showtopic=53 contains instructions to resolve the problem

cheers
anyweb

If you've not set up VISTA deployments, retrun to legacy mode only (RIS
only) ... that does it. Look at wdsutil /? for syntax.

"low_rider" <low_rider.2o1ejg@DoNotSpam.com> wrote in message
news:low_rider.2o1ejg@DoNotSpam.com...
>
> Hi there,
>
> I tried running this command, however I'm still getting the error
> message. I've used the correct Drive letter, still no go...
>
> Any ideas?
>
>
> Cheers,
> Low_ridEr
>
>
> --
> low_rider
> ------------------------------------------------------------------------
> low_rider's Profile: http://forums.techarena.in/member.php?userid=23846
> View this thread: windows-server-help/706832.htm
>
> http://forums.techarena.in
>

Its not broken you are trying to start a service that has been disabled by the install of SP2. If you look in Services you'll see a new service running called Windows Deployment Service. This replaces RIS, you'll also notice in the admin tools 2 new components, WDS and WDS Legacy. For your XP and 2003 images continue to use WDS Legacy as you would RIS.

Now that Legacy has replaced RIS you will need to Configure the DHCP Scope Options;
60 - PXE Client
66 - Name or IP of the server responsible for the images.
67 - OSChooser/i386/startrom.com This points to the image folder

Don't try to use WDS as this is used only for Vista and 2008 images. If you open and attempt to configure this option you will need a boot file and image file. This can be a major headache unless you're familiar with the process, and it will break Legacy if youre not.