1 of 1 people found this helpful
Prob 1. Known issue with Provisioning GUI and is being addressed. As for changing the service it is not recommended. You can read more about it here http://support.microsoft.com/kb/327618
Prob 2. Sorry but I'm having a hard time following, but it sounds as if you are saying provisioning task kicks off after the agent deployment, and while provisioning is chugging along, the scheduled tasks (required/push) kick in and there is a time where they are both running. If this is the case, one thing you could do is set a prerequisite for the scheduled tasks that you are deploying outside of provisioning. Something like this:
- Have a task in provisioning that sets a the prereq trigger. I would suggest writing a file or registry entry to the machine.
- Create a prereq query or script (depends on you) that looks for the file or registry key, if found fail. This will cause the scheduled task to NOT run.
- Have a task in provisioning that removes the prereq trigger at the end of the provisioning process.
- Schedule tasks will then process after the provisioning task.
- Make the scheduled tasks part of the provisioning sequence.
Thanks for your response.
Prob 1: Ok that’s bad. Without progress information the supporter doesn’t know how long the installation will take or any problems occur. I think we will switch the interactive option for the provisioning process and afterwards we change it back.
I hoped SP1 brings the solution but now we wait for SP2.
Prob2: This is a nice workaround but then we need to add this prereq for 300 individual packages and some of the packages need other prereq too. But we have only one prereq per package. This will not be a help for the administrative overview. Do you know other kind of workaround?
With regards to problem 2 you might want to take a look at this:
It'll prevent regular policy based SD tasks (or anything else) from running while Provisioning is still active.
Thanks for the link. This has solved our problem with the provisioning.
I might be shooting my self in the foot here but how did you change this option with the agent installation?
Did you just modify the service after the agent installs?
We have a few provisioning items that don't seem to run well in LDMS 9 but ran fine in 8.8 and I would like to try this.
if you mean the interactive option. Yes we change it directly after the agent installation and than we reboot the machine.
sc config cba8 type= own type= interact
I had tried this in Windows 7 but it didn't seem to work perhaps I'll try again.
But I just tried in XP and it works!