1 of 1 people found this helpful
What are you actually using for this command:
rscdversion –a –r –f1WINDIR\Temp\version-install_type.iss
Here is the command as it was entered;
C:\Windows\Temp>RSCD800-359-W32.exe -a -r -f1 c:\windows\temp\RSCD800-359-W32.iss
Is there a space in there that doesn’t belong?
Yes, there is a space between f1 and C that should not be there. Remove that space and run it again. Your command should look like the following:
C:\Windows\Temp>RSCD800-359-W32.exe -a -r -f1c:\windows\temp\RSCD800-359-W32.iss
I have a customer that try to upgrade agents to 8.2.
he tried recording an answer file using the command line:
RSCD82-SP2-WIN64.msi -a -r -f1c:\Temp\rscd_Upgrade82_64_Bit.iss (also /a /r)
This command doesn’t work
Does anyone has saw this problem before?
With the previous version it was with: RSCD*.exe and with 8.2 version we have: RSCD82*.msi,
Does the *.msi should work like the *.exe?
You do not need an iss file w/ the msi.
Hi Bill, So we need only to run a job with the agent installation, and if it's an old agent it will upgrade it automatically?
Yes.. just use a file deploy job w/ a post-install command of:
Msiexec /I rscd.msi /qn REBOOT=ReallySuppress
The title of that section says "To create a response file for windows agents earlier than 8.2" .....
you should be looking here:
The customer follow the procedure and execute the job, he got the following error:
Info 16:34:02 27/09/2012 "The Windows Installer Service could not be located. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."
He checked, and the Windows Installer service is started on the server.
I attached the message from the customer, it's look OK to me
error_message.jpg 136.4 K
what is in the post-install command for that job?
what user are you mapped to on the target system?