Explanation:
As an example: an install of service pack 3 with no problem using the -q -z -o switches. It completes with no problem. However when using using /q:a /r:n with an installation of any update the installation completes but returns the error code 3010.
Common Command-Line Switches for Self-Installing Update Files (Software may not support all switches listed here):
/q
|
Specifies quiet mode, or suppresses prompts, when files are being extracted.
|
/q:u
|
Specifies user-quiet mode, which presents some dialog boxes to the user.
|
/q:a
|
Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
|
/r:n
|
Never restarts the computer after installation.
|
/r:i
|
Prompts the user to restart the computer if a restart is required, except when used with /q:a.
|
/r:a
|
Always restarts the computer after installation.
|
/r:s
|
Restarts the computer after installation without prompting the user.
|
Common Switches for Service packs:
/f
|
Force other programs to quit at shutdown
|
/q
|
Quiet mode (no user interaction required)
|
/u
|
Unattended Setup mode
|
/z
|
Do not restart the computer after installation
|
What does error 3010 mean?
3010
|
The requested operation is successful. Changes will not be effective until the system is rebooted.
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
This isn’t really an error but is just a code stating that the operation completely successfully and requires a reboot to become effective.
What Switch is causing the problem?
The problematic switches in many of the scripted install process are:/q, /q:a, /z, /r:n.
These switches either suppress the prompt that tells the user that they need to reboot the computer for the install to finish or force the install without a reboot.
Solution:
When deploying these types of Scripted installs from either Deployment Server or Notification Server the solution would be these options:
Force a reboot after the install to finish the installation process within the script use the /f or the /r:a switches.
This is not merely a suggestion but a requirement in software delivery as far as Altiris Technical Support is concerned.
Two options in dealing with this error:
- Remove the /q:a or /q from the command line used. This will stop the occurrence of the 3010 error and then force the reboot of the client machine.
- Use Error handling within your scripts to work through that error. If with Software Management, add 3010 and 0 to the success codes in order to properly report a success
Here is a script example:
REM Installing Hotfix MS03-026
\\ServerName\express\server\common\packages\hotfix\q823980\q823980w2k.exe /u /z /q
if ERRORLEVEL 3010 goto success
if ERRORLEVEL 0 goto success
goto failure
:success
set %ERRORLEVEL% = 0
goto end
:failure echo Failed
EXIT 1
#goto
end
:end