anyweb

are you using ConfigMgr Beta 2 or Release Candidate 2 ?

have you tried installing the distribution point (which hosts the PXE stuff) on that server ?

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies. In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables. In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working. In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. In Part 13 we looked at how Role Based Administration is used within ConfigMgr and we created a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. In Part 14 we performed a side-by-side migration from Configuration Manager 2007. In Part 15, we deployed Windows 8 Consumer Preview to see if it was possible, and indeed it was (it's not supported by Microsoft however). In Part 16 we integrated MDT 2012 RC1 with Configuration Manager 2012 RC2. In Part 17 we configured MDT 2012 and used the UDI Wizard designer to configure the default Custom XML file used in a UDI task sequence. Now we will configure that XML file some more before creating a new MDT Task sequence to Deploy a User Driven Installation Client Task Sequence. We will then edit that task sequence to add Offline Language support and finally deploy it and monitor a client progress. Tip: This post is long and may take you some time to complete so do please give yourself plenty of time to go through it all. Step 1. Remove the prompt for Computername in our MDT boot image Note: Perform the following on the ConfigMgr 2012 server as SMSadmin In it's current state, when we boot our MDT boot image it will prompt the end user to enter a computername as you can see in the screenshot below we don't need this functionality as we will use the computer naming ability within the UDI wizard itself, so let's disable this. To remove the prompt locate your MDT Boot image in the boot images node, right click and choose properties Click on the Customization tab,the prestart command will look like this edit it so that it just reads WScript.Quit(0) then click apply as in this screenshot answer yes to update the boot image to your distribution points, continue through that wizard to completion. Step 2. use the UDI Wizard Designer to configure network settings and other changes Note: Perform the following on the ConfigMgr 2012 server as SMSadmin We already edited our UDIWizard_Config.XML file in the previous part but we need to make some additional changes to make it more user friendly and functional, so let's start up the UDI Wizard Designer again (start, programs, Microsoft Deployment Toolkit, UDI Wizard Designer). when the UDI Wizard Designer starts, click on the file ribbon and select our recently edited UDIWizard_Config.XML file. Select the BitLockerPage and remove the checkmark so that we are not prompted to enter any BitLocker info Next, double click on the New Computer Details Page and expand Network Details, select Domain scroll down further to Domains and OUs, click on the blue Plus symbol to add a domain when the Create or edit Domain Information window pops up enter your domain info and friendly text something like below.. click ok when done, to add a default OU right click on the added domain and choose Add OU Manually now you get the chance to add your OU information, so add it using the Distinguished name (which you can get from Active Directory) click ok when done, it should now appear something like this scroll down to Domain Join Credentials and add your domain join user account (I use one called Domjoin) Next open the Languages Page and add a few more languages (i'm using the scandinavian ones...) if you want, and then scroll down to the Volume page and select the User data and settings option, place a checkmark in the Format box... ok that's us done in the UDI Wizard designer so save your UDIWizard_Config.XML file to the Scripts folder of your MDT Toolkit Files package, and once done don't forget to Update your distribution points for the MDT Toolkit Files package. Step 3. Create Language Packs Note: Perform the following on the ConfigMgr 2012 server as SMSadmin If you have read my Customizing Windows 7 series you'll have seen that we added language packages offline using MDT 2010 update 1 in Configuration Manager 2007, we will use similar functionality here in Configuration Manager 2012 RC2 but with MDT 2012 RC1. But before we do, we need some language packages added. I will add Danish here and I expect you to add whatever languages you are interested in. In the ConfigMgr console click on Packages , select Create Pacakge from the ribbon or right click and select Create Package. give the language pack some useful name like Windows 7 X64 SP1 Danish Language Pack and details so that it's easy to find in the task sequence later on...click on Browse and select the folder where you have your Danish langauge pack (eg: \\sccm\sources\os\Windows 7 X64 Language packs\Windows 7 X64 - Danish) click next and then select Do not create a program click your way through the rest of that wizard. Note: when the package is created add it to your distribution points and update it to the dp's. Repeat the above for all language packs you intend to use in your UDI task sequence. once done we should have all the Language Packages we need and intend to use created and distributed like below:- Step 4. Create a MDT based UDI Client Task Sequence Note: Perform the following on the ConfigMgr 2012 server as SMSadmin We need to create a new MDT Task Sequence which leverages a User Driven Installation template, we will then edit it slightly before deploying to a Deploy Windows 7 X64 collection. So right click on Task Sequences and choose Create MDT Task Sequence when prompted to choose a template, select User Driven Installation Task Sequence from the drop down menu Note: In later versions of Configuration Manager 2012/MDT 2012 the wording in the template is changed from the screenshot above from User Driven Installation Task Sequence to Client Task Sequence and the option to select a User Driven Installation comes from within the Create MDT Task Sequence wizard, specifically when you get to the Deployment Method screen, choose User Driven Installation at that point to get a true UDI task sequence. See screenshot below for that setting. give the task sequence a name like UDI Client Task Sequence Enter domain details and Windows settings, nothing new here in fact we'll be using our UDI xml file to replace the network settings later... Select This task sequence will never be used to capture an image... select our previously created MDT boot image and our previously created MDT Toolkit Files package Next you get to specify the Windows 7 X64 image we captured in Part 7. specify the Configuration Manager Client upgrade package which we also created in Part 7 (Step 5.). and then specify the USMT 4 package and next we specify our MDT Settings package, have patience we are getting there :-) click next through to the confirmation message click Finish Step 5. Edit the Task Sequence to add Language packs Note: Perform the following on the ConfigMgr 2012 server as SMSadmin Language pack installation steps are not included in our UDI task sequence, so we have to add those steps, to do so right click on our newly created task sequence and choose Edit scroll down to the Post Install stage and to the Set Status 3 step (which occurs just before the Setup windows and configmgr step). This is where we need to add our new step(s) to install language packs offline. In the top left corner of your task sequence, click on Add, scroll down to MDT and choose Install Language Pack offline, these options are only available after MDT is integrated with ConfigMgr click on Browse and select your Swedish Language pack (or whatever language you are adding) click on the options tab for that step and add the following options, Task Sequence variable UIlanguage equals SV-SE Note: repeat the above process to add a new Install Language Pack Offline step for each Language you want to add, rename each step to correspond to the language you are installing and obviously the SV-SE task sequence variable in the options tab will have to correspond to the correct language, eg DA-DK for Danish etc.. click Apply and then ok the save the changes to your Task Sequence. Step 6. Deploy the Task Sequence Note: Perform the following on the ConfigMgr 2012 server as SMSadmin Right click the Task Sequence, choose Deploy choose the Deploy Windows 7 X64 collection set it to Available and make it available to boot media and PXE, continue through the rest of the wizard. once done, add a new virtual machine to your Deploy Windows 7 X64 collection, you can use this process if you wish. Step 7. PXE Boot a client and review the UDI process Note: Perform the following on virtual machine as a testuser After PXE booting our new virtual machine we get to see the list of available task sequences, note the really cool background ;-) after some moments of downloading the MDT Toolkit package, the UDI wizard appears ! and you can click your way (as a user driven installation is supposed to be done, by the end-user) through the wizard, the first screen after the welcome screen is the BItlocker screen, it's not enabled as we removed that option next we see the Volume screen, notice that Partition and format disk is selected already, we did that in the UDI Wizard Designer above. This is a new computer so we are not restoring any data, so click next at that screen the Deployment Readiness screen appears, this changes depending on New computer or refresh scenario and just lists the checks it performs you can retry checks in the event that you forgot to connect power to a laptop or whatever.. next you get the User Device Affinity screen, enter a primary user if you wish and click next, i guess you could call this the UDI UDA user screen and we can choose domain/OU based on what we entered in our UDI Wizard designer, enter the Domain Join credentials (password) to continue.. enter the local administrator password and specify a user (or users) to add to the local administrators group select your language and regional settings, notice how there are as many languages *listed to install* as you added in the UDI Wizard designer for the Install programs screen, you can see the apps we added earlier, you can select or deselect them and click next to continue, cool huh ? click next at the summary and let the installation begin, note how it shows you what stage it's on via a changing background picture and after some time the language pack you selected is installed and finally when the Deployment is complete you see the following, click on start windows to logon to windows Swedish Windows :-) job done.. cheers ! niall

did you guys remember to enable pxe support on the boot image itself ?

is your country listed ? this is taken from March 2012 Usage by Country for March 2012 Top 30 of 178 Total Countries # Hits Files KBytes Country 1 2186036 31.60% 1790928 32.24% 50594111 32.76% unresolved 2 1620069 23.42% 1200078 21.61% 28303283 18.33% commercial (.com) 3 987088 14.27% 864127 15.56% 25497285 16.51% network (.net) 4 184719 2.67% 90309 1.63% 2324481 1.51% Finland 5 144909 2.09% 120070 2.16% 3297446 2.14% India 6 129285 1.87% 111082 2.00% 3113063 2.02% Netherlands 7 128647 1.86% 103723 1.87% 3307272 2.14% Australia 8 114454 1.65% 96277 1.73% 2590607 1.68% United Kingdom 9 108606 1.57% 88841 1.60% 2904985 1.88% Germany 10 96751 1.40% 80476 1.45% 2321391 1.50% US educational (.edu) 11 88675 1.28% 74407 1.34% 2139024 1.39% Canada 12 81960 1.18% 67755 1.22% 2302600 1.49% Sweden 13 67343 0.97% 50834 0.92% 1463209 0.95% organizations (.org) 14 60342 0.87% 48703 0.88% 1674073 1.08% France 15 57015 0.82% 38385 0.69% 905353 0.59% US Military (.mil) 16 52285 0.76% 45137 0.81% 1478218 0.96% Belgium 17 49034 0.71% 36509 0.66% 973421 0.63% US governmental (.gov) 18 45768 0.66% 39615 0.71% 1428353 0.92% Switzerland 19 42375 0.61% 39861 0.72% 1125681 0.73% Poland 20 42293 0.61% 37492 0.67% 1364988 0.88% Norway 21 39773 0.57% 20633 0.37% 599382 0.39% Ukraine 22 36579 0.53% 32576 0.59% 820926 0.53% Italy 23 36192 0.52% 31696 0.57% 1148682 0.74% Denmark 24 35069 0.51% 29702 0.53% 675484 0.44% United States of America 25 34465 0.50% 31827 0.57% 1198510 0.78% Russia 26 31012 0.45% 27415 0.49% 961093 0.62% Brazil 27 26385 0.38% 20038 0.36% 507175 0.33% Turkey 28 24930 0.36% 17756 0.32% 586414 0.38% New Zealand 29 23330 0.34% 19246 0.35% 603962 0.39% South Africa 30 21492 0.31% 18793 0.34% 540264 0.35% Austria

what does the smspxe.log file reveal ? search for the MAC address of the client you are PXE booting

did you follow the guide exactly as it is ? if so you won't have issues. verify that the installation account for the clientinstall is a member of the local administrators group try disabling the firewall to see if that helps the ccmsetup.log will be present on the computer you are installing the client on

good info, did you not see this though, see the Note: ?

ok i've modifed the ruleset to exclude system as well as user context, please try it again (the new rules..)

just adding the following to this post - http://blogs.technet.com/b/oob/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

for the cleartext part, look at this post

you can create a package/program to uninstall the SCEP client as follows:- scepinstall.exe /u /s deploy that to a collection when you want to uninstall the SCEP client.

what steps did you undertake so far ? what did you do on the client side and on the server side.. here's a summary from Technet - http://technet.microsoft.com/en-us/library/gg699359.aspx Enrollment for mobile devices in System Center 2012 Configuration Manager is now natively supported by using the two new enrollment site system roles (the enrollment point and the enrollment proxy point) and a Microsoft enterprise certification authority. For more information about how to configure enrollment for mobile devices by using System Center 2012 Configuration Manager, see How to Install Clients on Mobile Devices and Enroll Them by Using Configuration Manager. After the mobile devices are enrolled, you can manage their settings by creating mobile device configuration items and then deploy them in a configuration baseline. For more information, see How to Create Mobile Device Configuration Items for Compliance Settings in Configuration Manager. For more information, see the Deploying the Configuration Manager Client to Mobile Devices section in the Introduction to Client Deployment in Configuration Manager topic in the Deploying Clients for System Center 2012 Configuration Manager guide.

sounds to me like your capture iso is faulty, can you try making it again please, how did you burn it to CD ?

there are no collections for FEP anymore as they are not required, there are no programs either, the SCEP client is now part and parcel of the ConfigMgr client. Please carry out all the steps in part 5 here to get a better understanding of how it works, and if you want to know even more, I'd recommend you purchase the System Center 2012 Configuration Manager Unleashed book when it ships and look at Chapter 16 which covers Endpoint Protection in great detail.

first things first, ConfigMgr 2012 is in release candidate you should NOT be rolling it out in production, period. MIcrosoft will not support you. secondly if you want updates from WSUS then it's all or nothing, so forget about using ADR's for the updates as ADR's require a working SUP and a working SUP wants to have full control of your WSUS infratstructure. Or, let Configmgr deliver all the updates, why use WSUS for software updates when you have a ConfigMgr infrastructure it makes no sense. SCEP can get updates in many ways have you reviewed all of them ?

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies. In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables. In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working. In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. In Part 13 we looked at how Role Based Administration is used within ConfigMgr and we created a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. In Part 14 we performed a side-by-side migration from Configuration Manager 2007. In Part 15, we deployed Windows 8 Consumer Preview to see if it was possible, and indeed it was (it's not supported by Microsoft however). In Part 16 we integrated MDT 2012 RC1 with Configuration Manager 2012 RC2 and now we will configure it to see what it can do with that integration by using the UDI Wizard designer to configure the default Custom XML file used in a UDI task sequence namely UDIWizard_Config.xml. Step 1. make the MDT boot image PXE bootable Note: Perform the following on the ConfigMgr 2012 server as SMSadmin After integrating MDT with ConfigMgr we created a MDT Task Sequence and as part of that wizard we created a MDT Boot image. This boot image gives us additional power and functionality over a standard ConfigMgr boot image (for example, we can display HTA's with this boot image without having to mount/unmount the boot.wim file and add additional support). Locate your MDT boot image in Software Library, Operating Systems, Boot Images, right click on it and choose Properties When the properties screen appears, click on the Data Source tab, place a check-mark in Deploy this boot image from the PXE service point. click OK when done. Step 2. Modify the UDIWizard_Config xml file using the UDI Designer Wizard. Note: Perform the following on the ConfigMgr 2012 server as SMSadmin As we will be creating a User Driven Installation Task Sequence in the next part, we first want to customise what our users will see when that wizard appears and to do so we need to use the UDI Designer Wizard. So click on Start, Programs, Microsoft Deployment Toolkit, and select the UDI Wizard Designer from the menu. The UDI Wizard Designer starts and you'll be presented with the new gui, we can use this gui to make changes to the built in UDI templates, they are simply XML files stored in the scripts folder of our MDT Files package. We could click on New to create a new XML file but let's import that one that the standard UDI Task Sequence uses namely UDIWizard_Config.xml. So let's load up that file from the copy we have in our MDT Files package, if you remember in Part 16 we created that package in \\sccm\sources\os\mdt\2012_rc1\files so let's click on Open in the UDI Wizard ribbon to browse to that location. type in the path to our MDT Files package namely \\sccm\sources\os\mdt\2012_rc1\files and click on the Scripts folder highlighted in the screenshot below a long list of xml files appears, scroll down to UDIWizard_Config.xml and click on it then click on open once the xml file is loaded you'll notice the wizard changes look, this is an overview of each page that the User Driven Installation task sequence wizard is capable of showing and here is where we configure them. But first, how do we make sense of this gui, i'll try and explain it briefly, in the Red box below you have the three main scenarios that we'll encounter during deployments sorted into StageGroups New Computer Refresh Replace If you expand New Computer you'll see a whole bunch of thumbnails for that StageGroup (and you'll also see New Computer.Prestaged below it), those thumbnails are what the User will see when the wizard kicks off later... note that depending on the scenario you are in, you'll be presented with different pages of the wizard. In the Left pane of the wizard you'll see the available pages listed alphabetically in the page library (not in the same order as they are presented to the end-user). Double click on one and you'll see the configurable options for that page (you can single click and you might see those options depending on whether or not you are in Flow or Configure mode, that's those two tabs in the right pane...) Click on Install Programs in the Left Pane, the number 3 in the right is the number of stages this Page is available in (you can hover your mouse over it to see what they are). Notice there is a Configuration Manager button in the ribbon, click on it. This brings up the Site Settings box, fill in your Configuration Manager site server name and site code and click on Validate Site. Note: The message states that this is required to add software items. To make application(s) available on the software page, applications must be targetted at the provided collection namely All Systems. The All Systems collection is a Device collection (for your computers..) so please deploy a few applications to that collection. Double click on Install Programs or click on the Configure tab next, click on General Software in order to see a menu we need (you can also right click on General Software to see a menu) Now that we have these extra options let's click on the big blue plus sign to add software to group the Add Software to Group wizard appears, select I want to add an application and click next now the Software Selection Wizard appears (another wizard within a wizard), click on Select to search for an application (why not call it search..?) and that brings up another wizard to search applications.. if you know the name of your application type it in here or click on search, after clicking on search, any applications deployed to the All Systems collection and with the Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting set in the applications properties will appear in the list. The application setting is here... select one application from the list and click on Finish you're newly added application appears in the list repeat the above process until you've added all your cool apps... and finally right click on the Sample Application from the list and click on Remove Item Next, Click on the LanguagePage in the left pane and add the Swedish Language (or whatever language(s) you want) and finally configure our Wizard config by clicking on Wizard Config in the ribbon. The Edit Wizard settings diaglouge box appears, you can customize the name and the background (banner), the default bmp file itself is located in the path where you installed Microsoft Deployment Toolkit in the Templates\Disitribution\Tools\X64 or X86 folders. make your changes and click ok. Ok now that we've done some basic configuration of our UDI template let's save it. if all went well you'll see File Save Complete. you can verify that the XML file itself has changed by it's date/time Step 3. Update your MDT Files package. Note: Perform the following on the ConfigMgr 2012 server as SMSadmin now that you've made changes to your UDIWizard_Config.xml you will want to update the MDT Files package so that we have access to those changes in the next part of this series where we'll create and deploy a User Driven Installation Task Sequence. In Software Library click on Packages and locate your MDT Files package. Right click on it and choose Update Distribution Points thats it for this part, see you next time when we will create a UDI task sequence and deploy it ! and see what happens on the client side.

so you are trying to say that you want to do a reinstall is that correct ? by BOX do you mean Computer ?

if no command prompt opens then you must check your boot image properties (right click on your boot image), look at the Customization tab, is command prompt support enabled in there ? did you update the boot wim images to your dps ? these steps are covered in the guides already if you followed them from Part 1. the new Application model uses Applications in the Software library, the old model (kept for legacy) uses Packages and Programs just like we did in Configuration Manager 2007

glad you found it :-)

did you successfully PXE boot before this ? if so just delete the computer object, then re-import it

did you re-distribute your boot images to your dp's after enabling the command prompt support?

just so i understand you correctly, you've enabled command prompt support as per this guide (it's an option on the boot image), you press F8 during WinPE and a command prompt appears, at the point you type cd %temp% then cd SMSTSlog then notepad SMSTS.log ?

x:\windows\temp\smstslog\ is a directory, it should have one or more files in it, namely SMSTS.log,. do you see that file in that directory ?

this question was already answered here fyi.