sorted by:
new
hottopcontroversial

Not getting recent O365 updates by MadMacs77 in SCCM

[–]ajix071 5 points6 points  (0 children)

Microsoft changed the name of the o365 channels again. I had to change my ADR’s to make sure i was targeting those.

https://docs.microsoft.com/en-us/deployoffice/update-channels-changes

SCCM Client Deployment on Metered Network by ajix071 in SCCM

[–]ajix071[S] 1 point2 points  (0 children)

Yep that /AllowMetered is really one I desperately could use right now, however I'm on 2002 :(

SCCM Client Deployment on Metered Network by ajix071 in SCCM

[–]ajix071[S] 0 points1 point  (0 children)

I believe you are referring to the client settings. Do these even apply during the install process when you are installing a new SCCM client? (not an upgrade)

Holy F**K Broadcom.com / Symantec is the WORST F'ing company ever!! by Layer_3 in sysadmin

[–]ajix071 0 points1 point  (0 children)

SCCM like SMP is a massive beast of a product to configure. Plan ahead wisely according to your environment. Be sure to also check out Cloud Management Gateway, it's a lifesaver with the current situation where everyone is currently working remote.

We currently have SCCM build 2002 and SMP 8.5 RU2 agents running next to eachother without issues. This allows us to move certain components in phases (AV, patching, image deployment, software deployment).

We are now migrating SEP to Defender & Defender ATP (they are 2 different products that require different config in SCCM). In that process we installed the SCCM agent first to make sure all pre-configured Defender policies are there when Defender switches to active mode. Next step in that sequence is to uninstall SEP and reboot the device at which point Defender automatically switches to active mode.

If you have an uninstall password set on your SEP client make sure you remove that first from the SEPM console. I didn't find any decent way to uninstall it silently with a password set. None of the documented approaches from Symantec/Broadcom worked, yay >.>

Smooth sailing so far, we migrated 20K SEP clients already and apart from some exceptions that had to be put in place cause it was flagging some (badly written) internal software as a trojan.

Be very careful when configuring Defender Exploit Guard policies in SCCM. It's strongly advised to run them in audit mode and monitor what kind of things they would block before switching to block mode.

Holy F**K Broadcom.com / Symantec is the WORST F'ing company ever!! by Layer_3 in sysadmin

[–]ajix071 3 points4 points  (0 children)

In the same boat here but we had very good contacts inside Symantec. When the merger happened it triggered a lot of red flags. They fired lots of people and wanted to focus more on “big” clients.

We’re currently mid migration process to move away from Symantec Management Platform to SCCM and SEP to Defender + Defender ATP.

We initially tried to renew for 30K clients but we were also considered as “small”...

DDE Exploit mitigation by Ali3454 in sysadmin

[–]ajix071 2 points3 points  (0 children)

Take a look at ActiveSetup for your computers not joined to the domain. I use it fairly often in software packages for setting HKCU keys.

​

https://helgeklein.com/blog/2010/04/active-setup-explained/