WMP11 Deployment Woes [solved-ish]
I am attempting to do a silent install (well, a re-install, really) of WMP11 on a group (~2000) of WinXP SP2 machines. I have the package, collection, and advertisement setup in SMS. I know SMS is executing my install.cmd because I have an echo statement that adds a line of text to a file in c:\windows\temp.
I created a file called install.cmd that has only two lines:
[hr]
[hr]
As I said, WMP11INST.TXT is getting appended to, so I know the .cmd is running fine. execmgr.log just shows an exit status of 1, but doesn't say what happened. I know the command line above works because I've executed the install.cmd in a cmd.exe that is operating under the system account (created by using "at (time) /interactive cmd").
Anyone have any ideas? The reason I'm having to do this is because, when you run Media Player, you get an error that tells you to log of and log back on (I'll have to go to a machine and get the exact log). If you log off and log on again, you get the same error. Running the above command manually fixes the issue (I'm assuming it happened at some point during the image creation, but testing missed it).
Any help you can provide would be greatly appreciated!
I created a file called install.cmd that has only two lines:
[hr]
@echo "Starting WMP11 Install" >> c:\windows\temp\WMP11INST.TXT
start /wait %0\..\mp11setup.exe /Q /C:"setup_wm /Q:A /r:n /P:#e"
[hr]
As I said, WMP11INST.TXT is getting appended to, so I know the .cmd is running fine. execmgr.log just shows an exit status of 1, but doesn't say what happened. I know the command line above works because I've executed the install.cmd in a cmd.exe that is operating under the system account (created by using "at (time) /interactive cmd").
Anyone have any ideas? The reason I'm having to do this is because, when you run Media Player, you get an error that tells you to log of and log back on (I'll have to go to a machine and get the exact log). If you log off and log on again, you get the same error. Running the above command manually fixes the issue (I'm assuming it happened at some point during the image creation, but testing missed it).
Any help you can provide would be greatly appreciated!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
michrech
17 years ago
Just to update this subject :
I looked in http://itninja.com/question/how-do-you-roll-out-new-machines?2347&mpage=1&key=wmp11 and it was suggested that a registry key needed to be changed to skip the validation prompt. This, at least for me, did not work. When I clicked on "mp11setup.exe", the first thing it prompted for was to validate. I have a feeling this is what is preventing my package from deploying properly.
Any ideas? The thread I mentioned above is from late 2006/early 2007.
As always, thanks in advance for any help!
I looked in http://itninja.com/question/how-do-you-roll-out-new-machines?2347&mpage=1&key=wmp11 and it was suggested that a registry key needed to be changed to skip the validation prompt. This, at least for me, did not work. When I clicked on "mp11setup.exe", the first thing it prompted for was to validate. I have a feeling this is what is preventing my package from deploying properly.
Any ideas? The thread I mentioned above is from late 2006/early 2007.
As always, thanks in advance for any help!
Posted by:
nheim
17 years ago
Hi Mike,
does the install work, when executed by hand in the SMS client account?
The registry key for the validation prompt has nothing to do with a successful installation.
Regards, Nick
does the install work, when executed by hand in the SMS client account?
The registry key for the validation prompt has nothing to do with a successful installation.
Regards, Nick
Posted by:
michrech
17 years ago
From what our network guy tells me, it runs using the "system account" on the local workstations. So, what I did to test this, was to use "at (time) /interactive cmd" to open up a cmd.exe in under the system account. Running the install.cmd file in this way works perfectly.
ORIGINAL: nheim
Hi Mike,
does the install work, when executed by hand in the SMS client account?
The registry key for the validation prompt has nothing to do with a successful installation.
Regards, Nick
Posted by:
michrech
17 years ago
The problem with this package turned out to be with the command line itself:
start /wait %0\..\mp11setup.exe /Q /C:"setup_wm /Q:A /r:n /P:#e"
The %0 part was not turing into \\radium\smspkgd$\(packagedir) as expected. It did have the correct directory, but also had the mp11setup.exe at the end. This was causing the package to fail. :(
Until I can get it figured out, I've just hard-coded the .cmd file to point directly at the smspkgd$ directory for this package (since it should never change).
Thanks for all your help, guys!
start /wait %0\..\mp11setup.exe /Q /C:"setup_wm /Q:A /r:n /P:#e"
The %0 part was not turing into \\radium\smspkgd$\(packagedir) as expected. It did have the correct directory, but also had the mp11setup.exe at the end. This was causing the package to fail. :(
Until I can get it figured out, I've just hard-coded the .cmd file to point directly at the smspkgd$ directory for this package (since it should never change).
Thanks for all your help, guys!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.