Rocket Man

Have you deployed the SUG to the unknown computer collection?

Just started this partcular model and so far it has been very painful to say the least. I eventually got it PXEing by installing SCCM 2012 sp1 CU1 to my site server, there is additional functionality within this update that allows you to PXE boot this type of device. Have to say once installed it PXE'd as it should...bit slow though. Next barrier was the famous restart after the boot.wim has been downloaded(even after injecting the winPE4.0 into the new boot.wim). I had to also inject the management pack into the wim file which contains network drivers and storage drivers. Now my task sequence is selectable.(Eventually) After a few attempts the partioning did'nt seem to be right, it bombed out when trying to apply the OS. A few tweeks to the partitions and I have it just imaging now,(applying OS as i write).....I am doubtful for a successful OSD as there are a couple of other steps that HP reccommend after the winPE enviornment, it consists of 2 seperate packages, a root certificate update and a BIOS firmware update. Time will tell. EDIT: Well it finished but failed at the root certificate installation ( I see why...a typo mistake on my behalf).....Other than this the device is functional bar a few drivers missing which are hopefully contained within the 2 extra packages that HP recommend. goudviske If you need to get PXE working you will have to install CU1.

How about this, save it as a vbs script. Run it locally first to see if it is what you want before creating a package.. set WshShell = WScript.CreateObject("WScript.Shell" ) strStartMenu = WshShell.SpecialFolders("AllUsersStartmenu" ) set oShellLink = WshShell.CreateShortcut(strStartMenu & "\Software Center.lnk" ) oShellLink.TargetPath = "%SYSTEMROOT%\CCM\SCClient.exe" oShellLink.WindowStyle = 1 oShellLink.IconLocation = "%SYSTEMROOT%\CCM\SCClient.exe" oShellLink.Description = "SCCM" oShellLink.WorkingDirectory = "%HOMEPATH%" oShellLink.Save Rocket Man

Have you disabled the SCEP client interface in your policy?

Naming Computers is really for unknown computers (Out of box PCs). The variable OSDComputerName should be set at the collection level on the unknown computer collection. Follow this guide and you should be fine. If you do not want to add unknown computer support to your enviornment another work around would be to use computer association from here. Once imported into SCCM.... they are named but obviously they are not on the domain yet. Simply add these imported computers to a baremetal collection and push your Task sequence out to them via PXE. Have them join the domain from the network settings task of your task sequence and thats it. They are pre-named via the import and on the domain via the OSD deployment. (bit long winded way of doing it but should work) OR use this script: Dim sNewComputerName, oTaskSequence, sTSMachineName, bPromptName Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' Get the name the computer is set to receive and truncate to first 6 letters sTSMachineName = lcase(oTaskSequence("_SMSTSMachineName")) If left(sTSMachineName,6) = "minint" Then bPromptName = True ElseIf sTSMachineName = "minwinpc" Then bPromptName = True Else bPromptName = False End If ' Note: The wscript.echo commands are logged in SMSTS.log for troubleshooting. They are not displayed to the end user. If bPromptName = True Then wscript.echo "Detected that the computer name is scheduled to receive a random value. Prompting user to input a standard name." sNewComputerName = InputBox ("Please enter a standard computer name to continue.", "Computer Name", , 30,30) oTaskSequence("OSDComputerName") = UCase(sNewComputerName) wscript.echo "Set Task Sequence variable OSDComputerName to: " & sNewComputerName Else wscript.echo "Computer set to receive a standard name, continuing as is." End If create a package out of it and place a run command line task directly after partion disk. The command will be whatever you wish to name the script i:e promptforsystemname.vbs and also associate the package with the run command line step. The outcome will be directly after the partioning of the disk you will be prompted to add your PC name and continue. Thats it. I's not a ZTI installation......if you want this you could integrate MDT into SCCM and this gives you added functionality one been a type of autonaming......it can be configured to automatically name machines to the ASSET TAGs of the systems see this Rocket Man

Are you deploying the apps as available or manadtory? Deploy as available to user collections to avail of the Application catalog not software center. Deploy to systems and it shows in software center!

According to this it can be RAM error or more likely too many policies pushed out to a collection that these systems are members of? Multiple ADRs targeted at a collection perhaps?

The clients by default do nothing like this.....It takes approx 2-3 mins for the clients to intialize once booted to the CTRL+ALT+DELETE screen, so it is not the clients that is causing this it is something else maybe inconsitent HDD? Have you pushed out some type of configuration to these PCs so that next time they boot they will scandisk?

Hi Niall The language pack was Gaeilge, and can only be downloaded as an LIP.mlc file(interface Pack) not LP.cab. As I mentioned I had to convert it to a cab file. Anyway the bottom line was I was entering in the wrong code for the Task sequence variable OSDUILanguage value(Always the simple errors.. ). I was entering in en-ga and other variants, and directly after the apply windows settings I was fronted with having to manually choose the default language before the Task sequence would continue. After finding the codes from here I realised my obvious mistake the code is actually ga-IE. After making the ammendment to the task sequence variable value, the Task sequence OSD was successful with the default language in Gaeilge. The HTA frontend sounds great and looks great but in the enviornment Im in (Education) would not suit as ZTI is more suited as machines get refreshed anually with no enduser at the machines to choose from the HTA frontend. Rocket Man

Ok actually got this solved. For anyone who needs to install a LIP file these are the steps needed. Download the required LIP file(s) it will be a .mlc file. This needs to be changed to a .cab file. In order to do this download and install a program that can do this, I used Notepad++. Open the .mlc file with Notepad++ and save as .cab. For users who do not have MDT integration use this post and create an answerfile like the one below and attach it to the Apply OS Task, change the codes as desired. All codes can be sourced from here. I really wished i had to have found this code sheet before I spent hours trying to get it work. I was putting the wrong code in. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>xx-xx</InputLocale> <SystemLocale>xx-xx/SystemLocale> <UILanguage>xx-xx</UILanguage> <UILanguageFallback>xx-xx/UILanguageFallback> <UserLocale>xx-xx</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="wim://sccm/sources/os/7/rtm/x86/sources/install.wim#Windows 7 ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> OR use the MDT way from here with the variable answerfile and get the correct OSDUILanguage Task Sequence variable code from here Rocket Man

Hi Is there anyway to automate the installation of LIP (Language interface packs) using SCCM. I have English as my parent language and am trying to install a LIP ontop of this. After following this post and this post I can successfully get it installed during OSD time via either methods but really would like to set the default display language to the installed LIP automatically. If I use the answerfile in the first post after the system settings have been applied I get prompted to select which display language I want to use before it will continue on with the installation of the configMgr client and rest of Task sequence. If i do not use the answerfile it does not prompt but the default language is English, and I can manually add the LIP display language by going to control panel, regional settings etc... (So the LIP does get installed as I can select it) I think the problem is that this LIP I am trying to install is not actually a fullyblown Language pack and thus the reason why the answerfile does not work as it should. Is there any other way to achieve this automatically? I have looked at group policy and searched for scripts but there does not seem to be anything related to achieving this. The enduser could do this but they are locked down(No control panel) via GPOs. Rocket Man

Have you tried manually activating a full resync of updates from the console and then go back into the product catlog of the SUP to see if the it has updated? If you are running CM2012SP1 the catalog should update with these new product versions after a sync.

Yes this is true..but from what I'v tested so far rightclick tools is more responsive and has alot more functionality other than policy force and computer collection association.

Yes and is totally fine to use in conjunction with SCCM.........saves me a lot of time and effort.. especially when forcing clients to pull policies....just do the full collection in one click!

Is it a generic autologon username for all exam machines or is it a case that every machine has different autologon credentials?

Again, you can use the right-click tools to achieve this. One of the functions of these tools is computer collection association! Once requested it will show you all the collections the computer is associated with.

What about using the Application Catalog for this? This is a self service portal for end users to view any available software that can be requested or installed at anytime they wish!

You are building a custom image and trying to capture it so that you can deploy it via SCCM? It is cleaner to have no drivers injected into a finalised image, deploying system specific driver packages along with the Task sequence is the recommended way. There still should be no reason why you cant inject drivers and run a sysprep and capture Task to achieve this. When do you get this error 0x80070005, during sysprep or during capture process?

What silent switch are you using with the execution of the flashplayer.exe? You are deploying it with a silent switch so that it does not require user interaction?

You have made the task sequence available and not mandatory thus the reason why you see the "Press F12 for network service boot" at the end......if it was mandatory it would automatically start to download the boot.wim Also I see you are getting DHCP referral....do you have VLANs? If so you will have to set IP helpers to get rid of this.....it may work for a while or even forever the way it is setup at the moment..... but best practices is to have IP helpers configured.

Have you different departmental user groups? If so probably best to deploy it to these user collections as available over a period of time and then keep track in the deployment monitoring to see if they have installed it. Let them browse the application catalog for it. OR Use WOL at non-peak and schedule the deployment to the appropriate systems collections.

Thanks for the lead...... Looking at this I feel the way to remove this is to go to the deployment package in the console and right click and show members, delete the update MS13-036 (kb2823324) and update distribution points with the new package. Another classic example of maybe scheduling your ADRs' not to evaluate for atleast 3-5 days after Patch tuesday and a deadline for installation 1-2 days after this until updates have been fully tested and reports come in for issues like these if they arise.

Yes that is why I asked...there is no need to not unless you have clients on different subnets/VLANs then you can configure DHCP options to let clients know where the PXE server is and the location of the bootfile (not recommended but will work, maybe for a while), the recommended way is to have IP helpers. Anyway have you seen this article? http://www.windows-noob.com/forums/index.php?/topic/7789-pxe-boot-failure-after-upgrading-to-system-center-2012-configuration-manager-service-pack-1/ It may be your problem.

Is DHCP on the same server as your SCCM\PXE server?

Where in the Task sequence process do you get this error?