shawnyuen

Thanks all! Let me look into your suggestions!

Hi all, Would like to hear from the experts here. How do you deal with the above request for their environment? Background: Our environment has this shortcut key to be deployed to the users' profile desktop which is easy, I just create a application package with the shortcut in it copy and paste it over to all users' desktop profile. However the tricky part now is that now my boss wants it to deploy this shortcut on a permanent basis, meaning to say once the agent detects the shortcut is missing from the user's desktop it will push over again. Last time in SCCM 2007, what I do is that I set it to a long advertisement expiry date. In the new SCCM 2012, it is not possible to do that with application deployment. However I do know is that I can create a baseline to check, however it does not auto remediate which my customer want. Any of our members here have other work around? All suggestions are welcomed.

Guys I found the document. Thanks once again. http://systemscenter.ru/sccm2012.en/html/2240a538-f7c1-4118-8b7b-894950dd5c34.htm#importingwondowsdevicedrivers

Thanks guys! Right now we are using OSD to deploy images when new workstations comes into our office. Is there any nice guides out there that teaches how to inject drivers into the boot image? I'm pretty new here. Thanks for your wonderful advice.

Hi all, Right now we are using OSD via bootable media method. The drawback of this method is that if the media is unable to recongise the machine NIC card, I will have issues to deploy. As such I am exploring should we be using PXE or MDT to deploy OSD to overcome such issues. Any suggestions from our dear members here? Regards, Shawn Yuen

Thank guys! I will highlight to my boss that such call back is on a 'best effort' basis. Thank you once again!

Hi all, Lately I have stumble upon a challenge given by my boss. He is asking me to devise a process to cancel off or recall the Windows Software Update on a last minute basis. Is this possible in SCCM 2012? The closest I could think of is to cancel off the deployment once the patch has been deployed. But this does not necessary mean that the deployment could be kill off policy the moment hit delete right? Would like to hear from our members how do they do it if you have such requirements from the top. Any suggestions and advice will be greatly appreciated. Thank you!