phaustein
Posts: 859
Score: 32 Joined: 3/21/2005 From: Washington, DC Status: offline
|
Some of these methods work for small or single site operations and not large multi-tiered site. Others, hack the processes by removing files and fiddling with permissions, all of which have to be corrected for the operation to return to normal. This can cause additional problems if other admins are not on the same page and that the changes were not corrected because someone forgets to correct it. And most haven't addressed the download and execute option, if the system already downloaded the package to run at a later date changing permissions or removing the packages won't stop them from running. I have found that what I had suggested works the best overall in most cases, and I'll explain why. Changing the advertisement will effective change policy, so any new systems will discover the change and comply with the change. Forcing an update of the package will also affect policy as well and as mention for the advertisement new systems will discover the change and comply. But what is most important about updating the package is that it creates a new version of the package. So any systems that had the old version of the policy and try to request content, the site will inform them that the content is not available and they need to check in for new policy. This works for the download and execute method, provided the system checks in for policy. If the system has the old policy information and has downloaded the package completely and doesn't connect back to the network, then there nothing that can be done to stop it. But if the system does check-in or tries to complete the download, it will effectively stop the deployment. I am not suggesting that the option I have given is the only option or the best option, just the most effective one.
_____________________________
Hope this helps. Paul
|