Jump to content


thugusher

sccm 2012 r2 rogue deployment

Recommended Posts

you can use reporting in configmgr to find out, check out the report category Status Messages - Audit, it will let you see what administrative users have done recently.

 

all audit messages for a specific user.png

 

like below

 

audit.png

Share this post


Link to post
Share on other sites

Thanks for the reply Niall. My colleague deleted the affected Collection and Deployment (used to be called Advertisements). We unticked "Allow this distribution to respond to into PXE requests" on the DP's > PXE tab. Is there any other way we can clear PXE requests on the affected client machines i.e delete a reg key, clear cache e.t.c.

 

So when we enable PXE requests client don't pick up the old deployment. I hope this makes sense...

Share this post


Link to post
Share on other sites

you shouldnt delete the deployment, just disable it (more info here)

what you could try is removing the boot wim attached to the task sequence, that way those systems wont be able to boot if they have received the policy,

also, consider changing the PXe Password or setting one if one is not already set. Many things you can do, but once the computers have the policy they'll try to act on it....

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.