Hello Everybody 

I am using a Service Template to deploy a Service Tier in VMM.

Everything works as expected , but I have to Perform some Tasks when a machine in the Tier gets deprovisioned (via PS Script).

I tried the Pre Uninstall and Post Uninstall Script Type Options but both dont seem to be executed.

Maybe it is a lack in my understanding. But how is an uninstall Triggered ? Deleting the machine doesnt seem to trigger it. And where is the Script executed? On the machine itself or in VMM ?

Does anyone know a kind of Flow Diagram where I can get a deeper knowledge the Execution chain of Script Commands ?

Thanks in Advance

Hi  Sir,

>>Maybe it is a lack in my understanding. But how is an uninstall Triggered ?

Based on my understanding , "pre-uninstall" script is bound to that application , uninstallation that app will trigger it .

I would suggest you to use a simple command to test if it works (e.g  cmd.exe tasklist > c:\test.txt ).

In addition , that script file must be stored in VMM library .

Best Regards,

Elton Ji

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim 20 hours 50 minutes ago

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator 51 minutes ago

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Thursday, August 06, 2015 6:24 AM

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Thursday, August 06, 2015 6:24 AM

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Thursday, August 06, 2015 6:24 AM

This is how we did it. Remember you have to treat the last VM in a service differently depending on your scenario.

We used SCOJOBRUNNER to call an Orchestrator job to do our post cleanup. Works pretty well.

• Proposed as answer by Microsoft Jim Friday, July 31, 2015 10:23 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Thursday, August 06, 2015 6:24 AM