anyweb

add a boot image to your task sequence and try again.

do you have any QOS software/hardware on your network that could be causing issues ? have you checked if the switches inbetween the dp and the clients are ok ?

do you get the same error if you specify bdeHdCfg.exe -target default -size 300 -quiet instead (without the path)

it will be great, don't worry !

have you tried to redistribute/revalidate the package on that dp where it's generating the hash error ? what does the smsdpmon.log tell you about validation of that package ?

Microsoft staff will likely be raising a glass or two, thanks to the latest available data. According to new data released by StatCounter on Tuesday, the latest version of Windows, Windows 8.1 has overtaken its predecessor Windows 8 for the first time, in terms of internet usage worldwide. The research firm's data shows Windows 8.1 has grown steadily to 7.5 percent in August, passing Windows 8's share of 6.6 percent. In the UK market the software giant's operating system (covering desktops, tablets, and consoles) surpassed its older sibling in April, with the US following a month later in May. By comparison, Apple's latest versions of OS X have a combined share of 7.8 percent — a speck compared to Windows' overall reach. "Following a mixed reaction to Windows 8, perhaps because of its radical new look, Windows 8.1 appears to be winning over users," StatCounter's chief executive Aodhan Cullen said in prepared remarks. Windows 7 remains the world's global leader in the operating system space, data from the company suggests, with just over 50 percent of the internet usage share. But StatCounter data should always be taken with a pinch of salt, as ZDNet's Ed Bott previously explained. Compared to the latest Net Applications' data, which is generally considered to be stronger overall data, Windows 8 has a 6.3 percent share, while Windows 8.1 has a 7.1 percent share — totaling 13.4 percent. read the rest at ZDNet > http://www.zdnet.com/windows-8-1-overtakes-windows-8-worldwide-as-windows-xp-refuses-to-die-7000033199/

have you tried the below:- Identify the systems with a duplicate GUID Delete the c:\windows\smscfg.ini file from the client Run CCMDELCERT on the client (*) Restart the SMS Client agent (SMS Agent Host) A new GUID will be generated

you can create a new Deployment Package every month if you wish or reuse the existing, this guide is just one way of doing it and of doing it in an automated way, use whatever works best in your environment. If you do create a new deployment package every month you'll need to edit the ADR every month to point to a new Deployment package as by default, it will point to the previous one created when you last ran the ADR, so if you select 'new deployment package' and call it 'new package', then the following run it will already be pointing at the existing package called 'new package' so you'll have to edit it to point to 'new package #2' and so on...

looks like you need to add network drivers for the hardware you are booting to your boot.wim, the file you need to look at is on the client, press F8 and look for smsts.log in x:\windows\temp\smsts.log

as you are using Configuration Manager 2012 R2, things have changed between that version and the version I wrote the guide for see my note here Note: [update] if you are completing this guide using Configuration Manager 2012 SP1 then this option is not available, instead, select the WIM file from a previously captured WIM image or point to the Install.WIM file on the Windows media. Please see this post for details\ alternatively, complete the task sequence wizard, and then go back and edit that step to point to the installer

not exactly, but here is what you can do http://technet.microsoft.com/en-us/library/jj591551.aspx however, i'd suggest you don't go adding a CAS unless it's really necessary, instead you should just bite the bullet and get rid of the other primary, how many clients are there ?

we need to see your smsts.log file(s)

well are you sure the data is captured, what do your scanstate.log and loadstate.log tell you ?

how did they discover them, can you share that info

can you attach the smsts.log file showing this

151 members and growing ! if you havn't already joined please do so for some interesting information about the site

you can simply create a package containing a script to install the driver and deploy that to a collection containing those computers, or create an application of that driver and deploy that application to the same collection.

you need to figure out what process is using that port you can do it with an administrative cmd prompt like so netstat -an -p tcp -b that will list all ports listening on TCP and the corresponding process.

take a look at the following post it should clear things up http://www.windows-noob.com/forums/index.php?/topic/6629-using-system-center-2012-configuration-manager-part-8-deploying-applications/

you are correct, I describe the entire process here my point being, once you've added the updates did you update that wim to the dp's or not and are you sure your task sequence is using that wim ?

did you update the new image to your distribution points after injecting the updates ? and are you pointing to the new wim image in your deploy task sequence

Introduction More and more touch enabled Windows 8 hardware is becoming available, which is great news for us but it also poses some technical challenges. I recently had to image some Lenovo ThinkPad 10's with Windows 8.1 using UEFI network boot via System Center 2012 R2 Configuration Manager. Problem Imaging the Lenovo ThinkPad 10 using USB Bootable media posed no issue even though the same boot wim was used for UEFI Network boot. When booting this device using UEFI network boot all was fine until just after the nbp (network boot protocol) part of the process started, this was even before the PXE password was presented. The problem was that the video resolution was set to something like 800x600 which means displaying any sort of Frontend HTA or UDI wizard to end users will look terrible. A colleague of mine (thanks Magnus) started testing with unattend.xml, wpeinit and drvload and got some good results so I set about putting a working solution together in a task sequence. Solution We will use drvload to load the video driver while still in WinPE as one of the first steps in the task sequence, normally you do not need to do this however in this case it's required as the video resolution is unusable. Step 1. Download and extract the driver Download the Chipset driver for the Lenovo ThinkPad 10 from Lenovo's website here. Once done, extract it somewhere by double clicking on the EXE file. By default it wants to extract the drivers to C:\Drivers. Browse to the path of the extracted drivers and locate the GFX folder as shown below Copy the GFX folder and all files and folders within in to your Configuration Manager package sources share, for example \\sccm\sources\os\drivers\Lenovo\ThinkPad10\Video\GFX as shown below Step 2. Create a Package containing the driver In the Configuration Manager console, create a new Package in Software Library, Fill in the Package details and browse to the GFX folder copied above as shown below with no Program as shown below continue through that wizard until completion Step 3. Distribute the package to your distribution points Right click on the package and choose Distribute Content as shown below after selecting at least one distribution point continue through that wizard until completion Step 4. Edit your task sequence and create a new Group Open up your deployment task sequence (I used the CM12 BitLocker Frontend HTA available here) and create a new group called Lenovo ThinkPad 10 UEFI Video fix. Next, on the options tab create a new If statement, where ALL the conditions are true. The conditions to check for are: check if it's a PXE boot check if it's in UEFI mode check for the Lenovo MTM You can do this by adding the PXE boot check using the _SMSTSLaunchMode variable as shown below and add an UEFI bios check by using the _SMSTSBootUEFI variable as shown below add a new wmi query as the one shown below Select * FROM Win32_ComputerSystem WHERE model like "20C3%" so that the finished options tab look exactly like below Step 5. Add a Run Command Line to xcopy the video driver Next within the new group, create a Run Command Line step, make sure that the step occurs somewhere at the start of the task sequence before any HTA, Frontend or UDI wizard is displayed such as in the example below. This step will work fine whether or not you have an MDT Integrated task sequence as it uses the _SMSTSMDataPath variable. the command line of the xcopy is xcopy ".\*.*" "%_SMSTSMDataPath%\ThinkPad10" /D /E /C /I /Q /H /R /Y /S make sure that you point to the package created in Step 2 above. Step 6. Add a Run Command Line to xcopy the video driver Next, create another new Run Command Line, and use the following command line drvload %_SMSTSMDataPath%\ThinkPad10\kit59677.inf so that it looks like below Step 7. Otpional - Set the resolution with Unattend.xml Create a text file called unattend.xml and copy it to your Video driver package created in step 2 above, redistributed that package to your distribution points, the contents of the file should be as below <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> </component> </settings> </unattend> Create another run command line step to set the resolution using wpeinit /unattend:%_SMSTSMDataPath%\ThinkPad10\unattend.xml as shown in the screenshot below Note that the unattend.xml file will not work unless the video driver above is loaded first. Step 8. PXE boot and verify Make sure the unit is shutdown first. Then initiate a UEFI network boot (PXE boot) by holding the volume down key (right side) and Power button (top side). I used a USB 3 ethernet dongle attached to a USB hub and a USB keyboard. Select the LAN connection using your external keyboard or use the up/down volume control then the UEFI network boot process starts, press enter or it won't boot it boot's to the PXE password screen, notice the resolution is extremely low After entering the password you select a task sequence, again at this point the resolution is low (you could fix this by including the driver in the boot wim but that would increase your boot image size considerably for only one model.) it's starts the task sequence, and get's to our newly added group, which then copies down the video driver files then installs them using Drvload followed by setting the resolution to 1024x768 via the unattend.xml file (this was optional, if you choose not to do this it will default to the native 1920x1080 with tiny text etc...) Job done ! cheers niall. Related Reading Task Sequence Built-in Variables in Configuration Manager - http://technet.microsoft.com/en-us/library/hh273375.aspx Drivers for Lenovo ThinkPad 10 - http://support.lenovo.com/us/en/products/tablets/thinkpad-tablet-series/thinkpad-10

youll need to increase logging on that server for that component (offline servicing), do to so change the Log MaxFileSize registry entries as shown below to your desired value... the value below is the default size (2.5MB) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing

what does your smsts.log file say for each app ?

sure do have you seen this yet ? CM12 in a Lab - Why do I get a winload.efi (Status: 0xc0000359 error) when using UEFI network boot in System Center 2012 R2 Configuration Manager ?