![]() For sake of simplicity I call it “ CurrentOSDCollectionID”. We first create a new Collection Variable. ![]() And for sure you need to have the Deployment web service running ( Installation Guide). It is even possible to extend current OSD Task Sequences with the scripts used by MDT to take advantage of the Deployment Webservice for some initial testing to see the advantages of MDT yourself. It takes only a couple minutes to be done and doesn’t interfere with anything you have configured already. If you don’t use MDT at the moment you really should consider doing it now. The following example assumes that you are using OSD with MDT integration. This way we can use a generic approach to remove the computer from whatever collection is configured in this variable. If the TS executes, this variable will be available for us and filled with the ID of the appropriate collection. They suggested to simply add the same custom variable to each OSD Collection and then just add the CollectionID to this variable. The following is based on an idea from Richard Zuraff and Jason Scheffelmaer (give credit where credit is due □ ). ![]() So all we actually need to know is the current collection. Since Version 7.0 the Deployment Webservice ( Download) supports a couple methods that let us remove a computer from a specific collection and also to clear the last PXE advertisement flag. And there is still the caching on the PSP. But as we also remove the computer from the collection there shouldn’t be any bad side-effect. I understand that this has been created to avoid kind of a Deployment loop for computers configured to boot from network first. ![]() If the underlying problem has now been fixed the Tech (or End-user) might not be able to re-initiate the Deployment before you also cleared the last PXE advertisement flag of that computer. But it’s also helpful in cases where the initial Deployment failed. The latter is mainly interesting for testing purposes, where you need to re-image the same computers over and over again. ![]() Two of the administrative tasks you often have to do after a SCCM based Deployment has finished is removing the computer from the OSD Collection it has been added to start the Deployment (you don’t really want to leave a computer in a collection with an active OSD advertisement, do you?), and to clear the last PXE Advertisement flag in cases the Deployment has been started via PXE. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |