WDS initialisation error

[freytshy]

Hello comunity
I'm setting up a WDS environment and got stuck in the first initialisation
of the WDS service.
my system is setup with the following caracteristics:
HP DL320 g3
Windwos serve 2003 R2 sp2 english
BDD 2007
WAIK
Partitions: C: (NTFS, system, boot, primary part 50gb) and D: (NTFS,data,
extended part 200gb)
when I execute

"WDSUTIL /Verbose /Progress /Initialize-Server /reminst:"D:\remotenstall""

i get the following error:

An error occurred while trying to execute the command.
Error Code: 0x7B
Error Description: The filename, directory name, or volume label syntax is
incorrect.

when i try to initialize WDS with the wizard i get the same error: "The
filename, directory name, or volume label syntax is incorrect"

Anybody had a similar problem?

thnax, mike

[Or Tsemah]

You have a syntax error.
Why not try to use the MMC ?

Or.

"freytshy" <frey...@discussions.microsoft.com> wrote in message
news:5518D5E1-FB14-4903...@microsoft.com...
> Hello John, thanks for your hint, I just re-checked but still the same. I
> also checked that there are no open terminal sessions. anyway I´m trying
> with
> a fisical server and a virtual server. to latter I exclusively connect per
> console.
> I´m still trying to resolve this issue, if anybody else has a suggestion
> please let me know.
> Thanks Mike
>
> "JohnD" wrote:
>
>> I had this exact problem.
>>
>> It turned out that the problem was due to performing the install of WDS
>> through a Remote Desktop session.
>>
>> The solution was to remove WDS (through Add/Remove programs) and install
>> at
>> the console.
>>
>> It then worked!

--
Or Tsemah
YSIDE

[freytshy]

thanks Or!
i tried with mmc, console and cmd: its all the same

thanks anyway! Mike

[P-Dot]

freytshy: Were you able to find a solution to this problem?

I am having the same issue, and have had no luck so far in finding a solution.

Peter

[freytshy]

hi peter,
to be honest, i didn't and i gave up. in my case it must be something weired
because i managed to get WDS running in a virtual environment where i started
from the scratch installing a new AD and a new WDS server.

sorry i couldn't help!

[BOFH_John]

Has anyone successfully gotten past this issue? (Now might be a good time for
an MS person to chime in...)

[P-Dot]

It was the oddest thing, but eventually I got it to work. Originally, I was
using Windows Server 2k8 beta 3 and put the system in Active Directory.
After banging my head on my desk for a few days, I got an e-mail from
Microsoft stating that Release Candidate 0 has recently been released.
Figuring why not, I installed it, put the system on Active Directory,
installed WDS service, then started to configure the server.

This time, I did not get the strange error of file path not found and was
able to continue following the instructions as posted online for setting WDS.
Afterwards, I was able to install the boot.wim and server 2k8.wim with no
problems. Ultimately, I had more success with RC0 then with beta 3.

My suggestion is to try RC0 to see if that rectifies the file path issue.

-Peter

[BOFH_John]

Strange... I'm trying it on 2003R2sp2, so that won't help much. When you say
you "put the system in active directory" do you mean by dcpromo or just
joining the domain? This is starting to ring a bell from back in my Novell
days...
-John

[P-Dot]

John,

I pre-created the system in Active Directory and made it a member of AD-no
dc promo.

-Peter

[ectowii]

I have servers in the environment that are having this exact same issue.
Each server is already a member of Active Directory. I do not have the
option of upgrading to Windows 2008. I have tried to reinstall WDS with the
same result on each server. Legacy mode works fine but I cannot configure
Native.