How-to enable PXE in SCCM 2012

A little how-to to enable PXE in SCCM 2012.

First go to Administration -> Site Configuration -> Servers and Site System Roles. Select the correct server (if you have more than 1 servers) and right click on Distribution Point to open the properties.

Open the tab PXE.

Select Enable PXE Support for clients

Select Allow this distribution point to respond to incoming PXE requests (If you have more than 1 points)

Select Enable unknown computers support (this is needed if you want to deploy brand new clients)

You could also select Require a password when computers use PXE, but then you don’t have a Zero Touch deployment. Thus, not a full automated deployment.

Like this:

Ok, now we have activated PXE, and WDS will automatically installing on your SCCM server. WDS is needed for the PXE communication.

To change some settings in DHCP is not needed, everything will be changed automatically.

You can check often if WDS is available in Server Manager.

To continue with enabling PXE you have to change some settings in the boot image(s). They must be available for PXE.

Go to Software Library -> Operating Systems -> Boot Images and right click on Boot image (x64) and choose for Properties.

Click on the tab Data Source.

Select Deploy this boot image from the PXE-enabled distribution point and click on Apply.

If asked for an update, click Yes. The settings will be updated to the distribution point.

This can take some time. I’m using Hyper-V and made a new VM named CLIENT03. You have to change de network adaptor to legacy network adaptor. Only the legacy supports PXE. Go back to SCCM and make a new task sequence. I’m using a deployment of Windows 7. You can also test it without an advertisement.

This is the result.

And without an advertisement you get an after Connecting Server X.X.X.X.

Maybe a tip if PXE doesn’t work. You can also add 066 and 067 in DHCP. For 066 you have enter the FQDN of your SCCM server. For 067 is the path smsboot\x86\ (forget the x86 in the path, it work also for x64 OSD)

Check also the log in C:\program files\Microsoft Configuration Manager\Logs\SMSPXE.log for more information if the PXE boot doesn’t work and you get only an message.

Good luck!

Windows Intune v4 Getting Started Guide

Microsoft has released a new version for Windows Intune in December 2012. This update supports the new Microsoft’s operating systems, such as Windows Phone 8, RT and Windows 8 (Ent/Pro). The very important feature is the integration with SCCM 2012 (SP1)

This integration helps you to support the clients of Windows Intune, such as mobile devices and notebooks outside the corporate network, from a single location. You will run the scheduled tasks or distributions from the SCCM 2012 console to the managed Windows Intune clients.

Microsoft made a tutorial for the newest version. 1355761715-WindowsIntuneGettingStartedGuide-Dec2012Release (download PDF)

I’m busy with a new blog to show you the details of the integration with SCCM 2012. But first I have to configure my lab environment for supporting mobile devices over Active Sync and maybe the Windows Intune Exchange Connector.

Windows Intune: Wave D and SCCM 2012 Service Pack 1 integration

It took some time, but now I have finally tested the combination of Windows Intune and System Center 2012 Configuration Manager Service Pack 1. This function is new in the update of Windows Intune: Wave D (v4) and SCCM 2012 SP1. With this option you have the functionality to add the Windows Intune environment to the SCCM environment. You have the opportunity to manage your Windows Intune clients, such as Mobile devices, in SCCM 2012.

This integration feature is nice for users who are using Windows RT tablet or iOS tablet in a corporate environment. With this feature the administrator has the possibility to manage the Windows RT tablet from a single location. This will be also nice for a BYOD concept for the Enterprise that already has SCCM 2012 infrastructure.

Support for mobile platform in Windows Intune was in the previous version great, but in SCCM is that a little bit disappointed. So, with this integration, you have a good support for all mobile platforms, such as Android, Windows Phone 8/RT and iOS. Also you could make a new package for a mobile platform via SCCM. The wizard for that is customized and so you have the option to choose an installer, like an APK for Android, or for a direct link (deep link) to the appstore or market. This means that you don’t have to download the installer/file and add it in SCCM.

Let’s see. The integration is not difficult to configure. You have a membership/account by Windows Intune (30-days trial) With this account you have to connect SCCM 2012 with Windows Intune. After that the function will synchronize with Windows Intune. When it’s finished you have the possibility to manage de mobile device via the SCCM console or if you are not inside the corporate network you have the possibility to use the Windows Intune console but this only for the Windows Intune clients and not for the SCCM clients.

To add the subscription go to Administration -> Hierarchy Configuration and right click on Windows Intune Subscriptions. Choose for Create Windows Intune Subscriptions.

Click Next.

Click Sign In.

Sign in with your Windows Intune subscription.

Select “Allow the configuration Manager console to manage this subscriptions”, because we want to manage mobile devices via SCCM console. 😉

Select a collection. I’m using “All users”, but it’s better to make a new collection. Add the name of the company and select the correct site code.

Select the platforms. I have selected Android. For iOS, Windows Phone 8 and Windows RT you need a certificate. I don’t have a certificate and also devices to test it. I have only an Android 4.1 mobile for testing. Direct management doesn’t work for Android devices. They, Windows Intune developers, hoping that direct management is available in the next version, Wave E (v5). Direct Management is only working for iOS, Windows RT and Windows Phone 8 in the Wave D version.

Click Next.

Click Close.

Now you have added a subscription into SCCM 2012.

Now we have to install the Windows Intune Connector role in SCCM. Go to Administration -> Site Configuration -> Sites. Click Add Site System Roles in the menu.

Click Next.

Click Next.

Select Windows Intune Connector

Click Next.


Click Close

These are the steps to configure Windows Intune subscription in SCCM 2012. Next part is a howto configure Dirsync for Windows Azure and Corporate Active Directory.

Migrate Configmgr 2007 SP2 to Configmgr 2012 SP1

Ok, I have got a new blog post, finally! 😉

This time I’ll explain how to migrate to the newest version of Configuration Manager 2012. In-place upgrade is not possible for the Configmgr 2007 to 2012. Configmgr 2012 has a built-in migration functionality. This functionality replaces the in-place upgrade of the existing Configuration Manager infrastructure. So, that means we have to use a site-to-site deployment. We have to create a new destination hierarchy.

Read this for more information. Also handy which data you could migrate and which one not.

The setup:

  • Lab environment. (Simple hardware config, Pentium G620 with 32GB of RAM. ISCSI NAS with 1TB LUN)
  • Windows Server 2012 Hyper-V
  • DC01, Domain Controller Windows Server 2008 R2 (with the schema update from Configmgr2012 (it’s the same of Configmgr2007)
  • SCCM2007, Windows Server 2008R2 with SQL 2005 SP4 and the necessary prerequisites. (ISS,BITS, WDS, WSUS and RDC, for more information check HowTo install Configmgr 2007)
  • SCCM 2012, Windows Server 2008R2 (2012 is also possible in SP1) with SQL 2008 R2 SP2 CU2 (SQL 2012 is also possible) and the necessary prerequisites (check my blog how to install Configmgr 2012: Prerequisites)
  • Enabled the PXE services on SCCM2007.
  • I’m also using App-v (5.0) packages.
  • Don’t use the same site code. Site code must be unique.

More information about the SCCM servers:

SCOM 2007 server: This one is standard installation, PXE is enabled for OSD. Configure it and test it. You have to add some clients, packages, OSD and software updates. OSD has to work, this means you have to use a client computer/vm for testing.

SCOM 2012 server: I have installed the standalone version. I don’t use a CAS and Child site. If you want a CAS and Child you can also follow this how to for migration. I have only installed SCCM 2012 SP1 and the roles, like de Software updates point and Endpoint protection Roles.

If you are using Hyper-V as a client, then you have to import the Hyper-V drivers in SCCM 2007 and add the necessary drivers in the Boot Image. These drivers are added in the Boot Image:

  • Virtual Machine BUS
  • Network adaptor
  • Input (but I think this one is not necessary)

First you have to know is that SCCM 2012 uses only UNC. If you use local path locations in SCCM 2007 you have to edit the packages, driverpackages, and images to the correct UNC path before migrating to SCCM 2012. There is a handy tool to change this is easier. Check this site

Ok, let’s begin:

First go to the console of SCCM 2012 and go to Administration -> Migration. Beneath the folder Migration you have to right click on Specify Source Hierarchy.

Add the source credentials in the wizard. I’m using the administrator for SCCM. Also for the database.

After hitting the Ok button the gathering begins.

In a complex hierarchy you will install your top SCCM 2012 server (CAS) and connect that one to the SCCM 2007 Central Server to gather all necessary hierarchy info.

If you have more than 1 primary sites you will create an active source hierarchy for each SCCM 2007 site to the SCCM 2012 CAS to gather all info.

Secondary sites need to uninstall manually from the SCCM 2007 site. For installing a new secondary site in SCCM 2012 consider it if this still required. Maybe a Distribution Points (DP) role is enough as we can now throttle DP’s with SCCM 2012. Simplify hierarchy J

By default SCCM 2012 will check each 4 hours to keep the gathered data up-to-date.

If you receive an error maybe you have to turn off the firewalls on both servers, or configure the firewall. You have to use an inbound rule for all programs, any ports and remote IP address of the SCCM server. This must be on both servers.

The gathering is finished:

Right click on Migration Jobs in the menu beneath Migration and choose for Create Migration Job.

Follow the instructions in the wizard. Choose for a name and Job Type is Object Migrations.

Select the objects. I have select the most except to old versions of SCCM clients, hotfixes and boot images. Boot images are not necessary because of the new version of WAIK in 2012.

Change here the correct ownership if you have a complex hierarchy. For me was it simple, because I’m using only a standalone primary site.

Click Next.

Click Next.

Click Next.

Click Next

Click Close.

Do the same for Collection migration.

After that you have the objects and collections in your new hierarchy.