How to configure DHCP for PXE Booting on WDS or SCCM 2012/2016 successfully

In this post, I will be performing the configuration for Configuration Manager SCCM 2016 PXE booting.
Go to your DHCP server console and expand the scope you would like to set as your PXE subnet/network (In this case I will be enabling PXE to all scopes)

On the Scope navigate to Server or Scope Options the configure new options 066 and 067.

On the Boot Server Host Name add the FQDN or IP for the PXE/WDS server

On the Bootfile Name add SMSBoot\x64\wdsnbp.com for SCCM if WDS by itself then set Boot\x64\wdsnbp.com

On the Windows Deployment Services (WDS) Role Configurations

Set the Do not listen on DHCP ports

And also authorize this WDS server in DHCP

On your test machine boot up and press F12 to select boot option then select PXE or Network booting.


Now it's time to image your systems.

That's it! You have now deployed PXE booting on your environment.

How to deploy Registry keys via SCCM Application Deployment with PowerShell Scripting

Before you start

Create PowerShell Script and tested
Create Script Installer an Application
Testing machines preferably VM's

Powershell Script

After the script is created and tested place onto your shared Configuration Manager drive.

Create Manually specified application

Deployment Type

Make sure you fill in the General, Content, Programs, Detection Method, Requirements and any others.

Programs

powershell.exe -ExecutionPolicy Bypass -File ".\RegistryKeys.ps1"

Detection Method

Registry Key

Powershell

Ok on the Deployment Type and then on the Application, to complete your application packaging.

UPDATED: How to fix SCCM 2012 / 2012 R2 / 16 Reporting Services Issue (When users try to run reports it shows like the DefaultValue expression for the report parameter 'UserTokeSIDs' contains an error) Updated

Problem

Users have this error message when trying to execute reports.

Solution 1

The RBACReporting needs to be changed form 1 to 0
Go to regedit
Navigate to -> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SRSP

Click on EnableRbacReporting change the values from 1 to 0


Restart the SQL Services / Reporting

Solution 2:

1. Open  the Reporting Service Configuration Manager
2. Connect and then go to the Execution Account Tab and Specify the account
Note: It's recommended to use a service account with admin privileges on the SSRS DB and Instance.
3. Apply the changes and then Exit
4. Restart the SCCM and SQL/SSRS services then try to run a report and it should be fixed. 

 
The problem should be gone now. If you keep experiencing any other issues feel free to comment or just contact Microsoft.

How to set SCOM Maintenance Mode via Orchestrator 2012 / 2016 and SCCM Collections for Remote Servers and Desktops.

If you are an IT admin you know putting servers in maintenance mode schedules it's crucial to not bug all your colleagues with hundreds if not thousands of emails during the systems scheduled restart. Currently if you use SCOM 2012 or 2012 R2 you don’t have an actual Scheduled Maintenance mode groups as they have finally release on the 2016 version.

Step by Step

• On your Configuration Manager Create a collection with the members you will like to put in maintenance mode.
  • Example
    • ServerCollectionNameSat12AM
• Go to your Orchestrator console and create a new runbook.
• On you runbook you will need to following activities.
  • Monitor Date/Time
  • Check Schedule
  • Get Collection Members (SCCM integration pack)
  • Start Maintenance Mode (SCOM integration pack)

• After you have added the activities you will need to link them all same as above.
• Activities Configuration:
  • Monitor Date/Time

• Check Schedule

On this one you might be required to create a new schedule.
To configure, go to the Global Settings/Schedules then create a New Schedule



Then after creating your schedule assign to your Check Schedule Activity

• Get Collection Members (SCCM integration pack)

On the Collection Members Activity Add the Collection and Name

• Start Maintenance Mode (SCOM integration pack)

On the SCOM Maintenance perform the following tasks:

{Member Name From "Get Collection Members"}.DomainName : Microsoft.Windows.Computer:{Member Name From "Get Collection Members"}.DomainName

Make sure your syntax looks this way if not it will not work as SCOM will not read the name correctly.

• After Configuring the activities you should be able the Check in and Run (Start the Runbook)

You should be able to see the Log history. Mine worked as expected :)