the media is write protected

[Lewok]

I am trying to use a job queue to uninstall office standard and install office pro plus.

The uninstall works perfectly fine, i have put a 5 min wait in to see if that cleared the issue. it then starts copying the files down for the install that is where i then get the Deployment: Error: The media is write protected.

the install then fails and so does the sp3 install after it.

any ideas?

16:05:24> jl2js42 is online and responding to WMI requests

16:05:13> Job Queue: Initiating ‘Wait for host to be detected online’

16:05:13> Reboot/Shutdown: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

16:04:31> Reboot/Shutdown: Attempting to initiate reboot…

16:04:31> Job Queue: Initiating ‘Reboot (force, if required)’

16:04:30> Deployment: Error: The media is write protected.

16:04:29> jl2js42 OFFLINE

16:04:13> Deployment: Copying file(s) to jl2js42 …

16:04:13> Deployment: Queued file copy operation…

16:04:13> Deployment: Establishing connection…

16:04:13> Deployment: ‘install pro plus’ queued…

16:04:13> Job Queue: Initiating ‘Deployment (install pro plus):: FileToDeploy:: E:Office 2007 Professional Plussetup.exe%**%CopyEntireFolder:: TRUE%**%LeaveEntireFolder:: FALSE%**%RetrieveConsoleOutput:: FALSE%**%Command:: “setup.exe” /adminfile C:comparedocstempupdatesinstall.msp%**%Parameters:: /adminfile C:comparedocstempupdatesinstall.msp’

16:04:13> jl2js42 is online and responding to WMI requests

16:04:13> Job Queue: Initiating ‘Wait for host to be detected online’

16:04:13> Reboot/Shutdown: Reboot initiated successfully.

16:04:12> Reboot/Shutdown: Attempting to initiate reboot…

16:04:12> Job Queue: Initiating ‘Reboot (force, if required)’

15:59:12> Waiting 5 minutes…

15:59:12> Job Queue: Initiating ‘Wait 5 minutes’

15:59:11> Deployment: Exit Code: 3010 (SUCCESS – REBOOT_REQUIRED)

15:57:11> Deployment: Executing \jl2js42 -s -w “C:comparedocstemp” “C:comparedocstempsetup.exe” /config C:comparedocstempconfig_silent.xml /uninstall Standard

15:56:37> Deployment: Copying file(s) to jl2js42 …

15:56:37> Deployment: Queued file copy operation…

15:56:37> Deployment: Establishing connection…

15:56:37> Deployment: ‘uninstall office standard’ queued…

15:56:37> Job Queue: Initiating ‘Deployment (uninstall office standard):: FileToDeploy:: E:Off2007setup.exe%**%CopyEntireFolder:: TRUE%**%LeaveEntireFolder:: FALSE%**%RetrieveConsoleOutput:: FALSE%**%Command:: “setup.exe” /config C:comparedocstempconfig_silent.xml /uninstall Standard%**%Parameters:: /config C:comparedocstempconfig_silent.xml /uninstall Standard’

15:56:37> Job Queue: ‘install Pro Plus’ queued…

[Lewok]

extra to above if i run the deployment from deploy software it works fine. is just when i use the job queue

[doug]

Lewok – The issue appears to be that your job queue contains the following two items in succession:

Reboot (force, if required)

Wait for host to be detected online

However, the above lines in succession will be problematic. In this case what you really need is:

Reboot (force, if required)

Wait for host to offline and come back online

The issue is that when the reboot is initiated, if you have a “wait for host to be detected online” *immediately* after the reboot command, the host will be detected online before it ever reboots. This leaves you with the following in the log:

16:04:13> Job Queue: Initiating 'Deployment (install pro plus):: FileToDeploy:: E:Office 2007 Professional Plussetup.exe%**%CopyEntireFolder:: TRUE%**%LeaveEntireFolder:: FALSE%**%RetrieveConsoleOutput:: FALSE%**%Command:: "setup.exe" /adminfile C:comparedocstempupdatesinstall.msp%**%Parameters:: /adminfile C:comparedocstempupdatesinstall.msp'

16:04:13> jl2js42 is online and responding to WMI requests

16:04:13> Job Queue: Initiating 'Wait for host to be detected online'

16:04:13> Reboot/Shutdown: Reboot initiated successfully.

The deployment first begins just when the machine is actually about to go offline. So then just seconds later the machine is actually offline and in the midst of a reboot, but the deployment is still trying to execute. So, you need to make sure the machine goes offline and comes back online after a reboot. It is not sufficient to use “wait for host to be detected online” right after a reboot command since the host will be detected online before the reboot occurs.

I hope this helps.

-Doug

[Lewok]

As usual Doug is the man with the answers.

that is now working a treat.

thank you

Lee

[booster]

Hi guys

Take care with the following:

Reboot (force, if required)

Wait for host to offline and come back online

The deployment may stuck if no reboot was required (no OFFLINE flag).

Regards

Booster

[doug]

Excellent point, Booster. In cases where a reboot may or may not be initiated you are absolutely correct. However, in the above case “Reboot (force, if required)” is used. This will reboot the machine every time, so this shouldn’t be a problem. “Reboot (force, if required)” always reboots the machine. The “force, if required” flag tells BP to attempt a normal reboot first, but if a user is logged on, then BP initiates a forced reboot, which logs off the user and reboots immediately, regardless of any open or unsaved programs that might be running.

-Doug

[Author]

Posts