Deploy Office 2010 by using Group Policy - Invalid switch - "/config"

Question

Hi All,
We are following steps described in this article -
http://technet.microsoft.com/en-us/library/ff602181.aspx . However it won't work and will terminate with error code 1 - "Setup ended with error code 1". Further investigations has shown that error is produced by start-up batch script due to Invalid
switch - "/config". According to the above article to trigger an install we need the following:
start /wait %DeployServer%\setup.exe /config %ConfigFile%
However it will fail with the error: Invalid switch - "/config", because obviously "/config" switch does not belong to START command
It seems to work if we will use the following (without START /WAIT):
%DeployServer%\setup.exe /config %ConfigFile%
Could anyone please elaborate on the above?
Also why would we want to use START /WAIT at all?
TY

Answer 1

So, you figured out that this problem occures if path to deployment share, config.xml and setup.exe has spaces in it, that is absolutely true.
But I see another workaround, not changing your share path to have no spaces in it.
I suggest changing the setup script.
Do the following:
1) Find this part of the script:
REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
2) Use quotes wisely to get something like this:
REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait "%DeployServer%\setup.exe" /config "%ConfigFile%"
echo %date% %time% Setup ended with error code %errorlevel%. >> "%LogLocation%\%computername%.txt"
As you can see, I used quotes to mark those parts of scipt that will have spaces in UNC paths when running the script in cmd.
It did the trick for me and i have spaces in my UNC path to setup share :) Hope that helps.