28 בApril 2018
Hey guys, if you recall, a few months ago I posted a great new article about a new security possibility called Exploit Guard -In that article, I did my best to summarize everything related to configuring and applying this security possibility using Group Policy. If you want to read more about this, please follow this link:
So, today I’d like to go over how to deploy this security possibility to accomplish the same purpose using SCCM.
We already know a little bit about Exploit Guard requirements:
Attack Surface Reduction Devices must have Windows Defender AV real-time protection enabled.
Controlled folder access Devices must have Windows Defender AV real-time...
19 בApril 2018
It is quite well known and not a secret that Microsoft wants being involved and be a major player in anti-virus worlds, they are increasingly pushing the endpoint protection as security solution to many customers, and to be sincere the Endpoint protection does a perfect job!
In this article, you are going to see how to enable and deploy the SCEP (System Center Endpoint Protection) and afterward, I will show you how to create the necessary antimalware policy and custom client device settings and at the end, we will deploy them together.
System Center Endpoint Protection allows us to manage our end clients...
12 בApril 2018
I gonna show you how to change SCCM Boot Image background during Task Sequence deployment.
It's going to be pretty straightforward, just changing the default background image with yours.
You should find out where the "Windows PE Background" is located using check the WinPe properties:
You should update the 86 & 64 boot images with the same background image
Go to your boot images and right click on them and then click on "Customization" and you will see the "Windows PE Background":
By the way, almost forget, This is the default one which comes with boot images:
Browse the folder that contains the background...
10 בApril 2018
During the week I have experienced a very annoying issue with Office 365 on terminal servers.
You may get the following message while opening an office product on terminal services:
This copy of Microsoft Office cannot be used on a computer running Terminal Services. To use Microsoft Office on a computer running Terminal Services, You must use a Volume License edition of Office.
although you have installed your Office according to Microsoft best practice with "SharedComputerLicense" value in the XML:
<Property Name="SharedComputerLicensing" Value="1" />
In order to verify if you have installed the correct version you should open the registry and find the following key:
3 בApril 2018
Sometimes you could see the following Event in the Event Viewer on Exchange 2013, I don't like seeing these messages on some critical systems.
You would check the MoveRequest and verify if any mailbox move request is stuck or export requests, import requests of migration batches, you should wait, remove, delete it up to you.
You can fix this using the following cmdlet:
Remove-MoveRequest -MoveRequestQueue "DatabaseGuid" -MailboxGuid "RequestGuid"
Afterward, you shouldn't see that message on event viewer, unless you have another warning about the different mailbox.