anyweb

you are looking in the wrong place for example if it's a deployment for an Application, go into software library, locate the app itself and click on the deployments tab, you can then select your Deployment and right click, delete

nothing has been said, so we are all in the dark, just like you

i've alerted the DOCS team and they will change the wording to spell this out clearly during the next scheduled Documentation Update

well it's not that obvious and I just checked the Docs, they state which still doesn't reveal that you must Deploy to a User collection in order for this option to be valid, however the actual option "Require administrator approval if users request this application" does mention users specifically and not Systems/Devices so hopefully that clears it up cheers niall

correct, you must deploy it to a User collection try it and see

what collection is it Deployed to ?

show me a screenshot of what you are seeing

well to spread the load, put your virtual machines on different SANS to increase your IOPS

smsts.log file should reveal the issue (on the client you are trying to capture)

feel free to post some guides for the rest of us , actually when editing my changes live i use notepad in WinPE on the live code then press F5 to refresh the result

notepad ++ is all you need, and then copy the bits and pieces that you find on the internet and you'll be good to go, what else do you need ?

or incorportate mdt and with ztiutility it will log to whatever your script is called, eg: mycustomscript.log

This post is an addition to Part 4 where we installed Language packs on a one-by-one basis (i.e. one language pack selected, one installed, one keyboard layout selected, one installed). What if you want to install multiple Language packs and multiple Keyboard Layouts well this is how to do it...but before we continue, make sure you have successfully completed Part 4 before attempting this. To make this possible I adapted the windows-noob.com Multipurpose FrontEnd HTA so that i could select Multiple languages and Multiple Keyboard Layouts, this change is only a minor one to both the backend script (HTA) and the task sequence itself, so rather than explain all about them i'll post this bits you need to know here. Also, I havn't ported these changes yet *but will soon* into the BitLocker Frontend HTA which I think looks much cooler, so I hope that you check that one out also. So where do we start, with the actual frontend HTA backend code.. aka, the HTA itself. The following section has been changed in the Deploymenu.HTA file, <tr> <td class="taskTableLeftCell" >Regional Settings</td> <td colspan="3" class="taskTableSpanSecondAndThirdCell"> <select name="regionDropDown" id="regionDropDown"> <option value="None">None</option> <option value="Multi">Multi</option> <option value="En-US">En-US</option> <option value="sv-SE">sv-SE</option> <option value="da-DK">da-DK</option> <option value="nb-NO">nb-NO</option> <option value="fi-FI">fi-FI</option> </select> </td> </tr> <tr> <td class="taskTableLeftCell" >Language Settings</td> <td colspan="3" class="taskTableSpanSecondAndThirdCell"> <select name="languageDropDown" id="languageDropDown"> <option value="None">None</option> <option value="Multi">Multi</option> <option value="English">English</option> <option value="Swedish">Swedish</option> <option value="Danish">Danish</option> <option value="Norwegian">Norwegian</option> <option value="Finnish">Finnish</option> </select> </td> </tr> the new bits in both drop down menus (regional/language) are this <option value="None">None</option> <option value="Multi">Multi</option> and they offer us the ability to set nothing (and get the default en-US/English) or to select Multi or to select ONE language or ONE keyboard layout. The MULTI option is special. It simply sets a variable which will run a group of steps to select multiple languages and/or keyboard layouts in the task sequence. The screenshot below shows both Regional (keyboard layout) and Language options have been set to Multi via the drop down menu. Setting the Regional options If we select Multi for Regional options then the following group is run in the task sequence the Options tab is where it detects the RegionValue variable value and if it equals Multi this group is executed the first step of the group sets the OSDInputLocale variable and it sets the Default keyboard layout (the first one listed) and the remaining available keyboards added to windows the values in that step are as follows en-US;0409:00000409;da-DK;0406:00000406;fi-FI;040b:0000040b;sv-SE;041d:0000041d;nb-NO;0414:00000414 Note: You can get a list of these values on MSDN here. the remaining steps of this group simply set OSDSystemLocale and OSDUserLocale to be equal to en-US. Setting the Language options The first step of this group (which only runs if the LanguageValue variable=Multi) is to set the OSDUILanguage, I set it to en-US. The next step installs the Language pack offline. The only magic here is in the language package, it must contain ALL of the language packs you intend to install as part of your Multi Language installation, so in my example I install 4 languages, Swedish Danish Finnish Norwegian and all those language packs are in my Offline Nordic Language Pack. Your multi language pack could contain however many languages you intend to install as a group, but the more you add the longer the install will take. What is the result ? so what do you get when it's all done ? you get the ability to use a drop down keyboard selector on the Windows 7 login screen and you can choose the same keyboard layouts within Windows and the languages are available also jod done, i'd say :-) Download the goodies Here's the updated task sequence and HTA files, you dont have to use a HTA to set the variables you can do that via collection variables or some other method but doing it in a HTA is cool. People will like you more. DeployMenu.zip have fun ! cheers niall

if it's not creating the folder then possibly it's skipping the group/steps altogether, did you verify that it's running those steps ? try adding a pause to verify

you can remove it, wait and then re-add it no problem, no need to do anything with your packages.

try a run command line step with the command listed above...

not using this method as its unsupported and missing some vital files, in my guide i purposely disable the capture group, you can still capture it with imagex

disable the entire Capture group and it'll work just fine.

check your bdd_pkgmgr.log.txt what does it say, it will be in c:\_smstasksequence\smsosd\osdlogs\ while the language packs are installing (but not after)

how did you create your language package ? did you use the sp1 language package or windows 7 lp ? what does your bdd_pkmg.log file reveal ?

good questions, 1. not sure yet, will have to find out when that happens but i would assume that the superseded updates will overwrite the old ones. (ie: replace) 2. no unless you remove the configmgr client first as they are different hierarchies and versions.

that version of SQL is not supported, the supported versions are listed below:- Database Requirements SQL Server 2008 SP2 with CU 7 SQL Server 2008 R2 with SP1 and Cumulative Update 4 SQL Server Express 2008 r2 WITH SP1 and CU 3 is supported only on secondary sites SQL Reporting Services is ONLY reporting solution For Supported Configurations information, visit http://technet.microsoft.com/en-us/library/gg682077.aspx.

are you applying any network drivers in an apply driver package step ? what hardware is this ? virtual ?

what does your smsts.log file say about the error ?

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). Now we will integrate the recently released MDT 2012 RC1 with Configuration Manager to avail of new features (features and enhancements which can help to make large-scale desktop and server deployments smoother than ever) that it provides through MDT Integration. Having MDT integrated with ConfigMgr will give you lots of benefits and abilities so I would definitely recommend you integrate it. Note that in order to download this build of MDT you have to be registered with the MDT program on Connect. Step 1. Download MDT 2013 and Install it. Note: Perform the following on the ConfigMgr 2012 server as SMSadmin MDT 2013 is available from the following location. As we are using Server 2008 R2 (64bit OS) we will download and install the 64 bit version of the software (MicrosoftDeploymentToolkit2013_x64.msi). If your ConfigMgr console is open, close it and then install the MSI by right clicking on the downloaded MSI file and choose Install. when the open file security window appears choose Run the Welcome to MDT wizard appears, click next accept the EULA if you want to continue and click next and next you get to choose where you want to isntall MDT, we will install it on D:\Program Files\Microsoft Deployment Toolkit\ so set your path accordingly click next, and then click Install answer yes to the UAC prompt and finally it's installed by clicking Finish. Step 2. Integrating MDT with Configuration Manager Note: Perform the following on the ConfigMgr 2012 server as SMSadmin Now that you have installed MDT you want to integrate it (Configure ConfigMgr Integration) with ConfigMgr. We do this to gain access to tools and features that MDT provides from within the ConfigMgr console. In the start menu, locate the newly installed Microsoft Deployment Toolkit application and expand it, locate the Configure ConfigMgr Integration shortcut and right click, choose Run as Administrator. click yes when prompted by UAC review the pre-populated options and click next and review the Confirmation, make sure there are no issues reported otherwise your MDT Integration has failed Step 3. Create a MDT Task Sequence in ConfigMgr Note: Perform the following on the ConfigMgr 2012 server as SMSadmin We need the following MDT components to be created: MDT Boot image MDT Toolkit Files MDT Settings To create these MDT components so that we can use them later on, we run a wizard by creating a MDT Task Sequence. The wizard will guide you through creating these packages. The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA. Start up the ConfigMgr console and browse to Software Library, Operating Systems, right click on Task Sequences and choose Create MDT Task Sequence. Choose a Template, there are several provided in the drop down menu, we will choose Client Task sequence fill in the Task Sequence name and comments for Details, fill in your Domain Join credentials We are not going to catpure an image with this Task Sequence, as we are only using this Task Sequence to create the needed MDT Files and Settings packages... for boot image, specify a previously created (empty folder) UNC path, eg: \\sccm\sources\os\boot\mdt\i386 fill in some MDT boot image details and for options specify the X86 architecture and set your scratch space (environment for MDT to use in WinPE) to 128MB (to allow drivers etc...) next select your optional WinPE components (language, MDAC/ADO support and PPoE) and fill in your prestart, extrafiles and wallpaper options (all optional), make sure to leave F8 command prompt selected Next we get to create our MDT Toolkit Files package, so select the Create a new Microsoft Deployment Toolkit Files package option, point it to a previously created path such as \\sccm\sources\os\mdt2013\files fill in details about the MDT Toolkit Files package..be descriptive as it's common to have different versions of MDT Files in your lab (in the future) for OS Image, specify an exiting image, select the Windows 7 X64 image we captured in part 7 and then select our previously created Configuration Manager Client Package and our previously created USMT 4 package for the Settings Package, we choose to create a new Microsoft Deployment Toolkit Settings Package, point it to \\sccm\sources\os\mdt2013\settings fill in the Settings Package details choose No Sysprep package and click next through the summary to Confirmation, answer Yes to any UAC prompt that may appear, at this point you can go take a long coffee break as this takes quite some time to mount the WIM image (boot) and create the packages and do it's magic.. and finally it's done ! Step 4. Distribute your new MDT packages and boot image to your distribution points Note: Perform the following on the ConfigMgr 2012 server as SMSadmin At this point, i'm sure we are all aware how to distribute content in ConfigMgr, and now we have some new packages (MDT Files, MDT Settings) and a new MDT boot image to distribute to our dp's. I'll show you how to distribute one of these, you can do the rest. Select the MDT Settings package in Software Library, Packages, right click it and choose Distribute Content select your distribution point(s) and continue through the wizard.. Note: Please don't forget to repeat the above process for the MDT Files, and the MDT boot image. In the next part of this series we'll look at what we can do with MDT within ConfigMgr.