How to get rid of Personalize and screen resolution in the context menu when you right click the desktop

The powershell script in this article will delete personalize and screen resolution on the context menu(right mouseclick on desktop). this is usefull for VDI or RDS environments. It is only working with software deployment or task sequence deployment in SCCM, because it is designed to run with system account privileges.

Download the word file copy the text to notepad and save the file as <yourname>.ps1

Deletecontextmenuitems

Noscreenresolutionandpersonalize

 

Advertisements

Powershell Examples calling wmi SCCM client

#Get-WmiObject -Namespace root\ccm\clientsdk -Class * -List
#Get-WmiObject -Namespace root\ccm -Class * -List
#Get-WmiObject -Namespace root\ccm -Class SMS_Client
#Get-WmiObject -Namespace root\ccm\clientsdk -Class CCM_Program -List | select -ExpandProperty Properties
#Get-WmiObject -Namespace root\ccm\clientsdk -Class CCM_ClientUtilities -List | select -ExpandProperty Methods

#Get-WmiObject -Namespace root\ccm\clientsdk -Class CCM_InstalledDeploymentType -List | select -ExpandProperty Properties
#
#Invoke-WmiMethod -Namespace root\ccm\clientsdk -Class CCM_InstalledDeploymentType -Name Id
#
$versionSCCMclient = Get-WmiObject -Namespace root\ccm -Class SMS_Client | Select -ExpandProperty ClientVersion

IF ($versionSCCMclient -ne “5.00.7958.1401”) {

Write-Host “Old Version start upgrade”
CMD.exe /C msiexec.exe /p configmgr2012ac-r2-kb2994331-i386.msp /L*v %TEMP%\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
}

 

 

Add driver package not applied in OSD server 2008R2 and OSD error 31 on Server 2012R2

last days i had the following symptoms/failures with OSD in SCCM 2012 r2:

– Migrated server 2008 r2 task sequence deployment has failed to Run. VMWare VMXNET 3 drivers dont get injected or applied in the OS. Ethernet controller is missing in device management.

– New server 2012 r2 deployement fails with error code 31. Exiting with code 0x80004005 Windows setup failed, code 31.

– After troubleshooting for a day i wasnt able to build and capture task sequences with Operating System Installers in sccm 2012 r2.

 

I thought build and capture wizard had a bug. after googling i found the following article. wow Microsoft just changed the working!

see this article. This is a nice article also. Helps you with OSD

What’s New in System Center 2012 Configuration Manager SP1

The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor. :(:(:(
After selecting “Apply operating system from a captured image” instead of “Apply operating system from an installation source” and run the deployment it was successful!

SCCM ADR download – Security Rights

// // //

When you run download and distribute updates in the SCCM console manually it is using you credentials to download and copy the files to the Package Source, when you use an automatic rule the SCCM Site Server’s computer account is used.

WSUS on S2012 installs with WID, even when it is de selected

With the GUI /Server Manager Roles and features: When you install WSUS on server 2012 and you want to make use of SQL for the Database and de-select WID it just installs the WID services!!

Check this article for de-install of WID

When you install it with the commandline syntax WID everything is fine.

Install-WindowsFeature -Name UpdateServices-Services,UpdateServices-DB –IncludeManagementTools

PS C:\Program Files\Update Services\Tools> .\wsusutil.exe postinstall SQL_INSTANCE_NAME=<servername\instancename> CONTENT_DIR=<path_to_content>

When WSUS doesnt work follow this article. Post install log gives the following error: 2014-08-19 16:24:36  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

OR just follow this:

– Remove WSUS Administration in IIS.

– Start .\WsusUtil.exe postinstall.

 

All credits to Jorn. 🙂