UDI feature
SCCM 2012 Question about 32 Bit vs 64 Bit Images - Confused Machines
Hello,
I have a question that I'm curious about, and I'm hoping someone can help me out. I am new to SCCM imaging, and have started running into a issue. When I deploy the 32 bit image to my labs, some of the computers tell me that they can't image because the image is a 64 bit image. I'm not sure why the machines are getting confused? The bad part is that the machines that are having the issue are sporadic, it's not every machine with the issue. I have tried to delete them out of the active directory, and out the SCCM. Thought maybe if I started from fresh that would help the issue. I am using HP 5100DC with Windows 7 for the operating system. Any help you can give me would be greatly appreciated!!
Thank you in advance,
Ang
Removing old computer object in AD during OSD?
I'm looking for a way to delete old computer objects from AD during OSD.
The scenario is this:
The old naming standard for computers were WS-%macaddress%
The new naming standard is supposed to be LKP-A%serialnumber%
The problem is that whenever a computer is reinstalled, the old computer object in AD remains.
Preferable not removing my CustomSettings (the Gather step)
I've been looking at various PowerShell scripts, but I know NOTHING about Powershell, so it always ends with doing something else.
So if possible, I would like to avoid using PowerShell.
MDT Task Sequence Error 80070002
Version - SCCM 2012 R2 CU1.
When the TS runs at one of our sites it fails on the first package that tries to download. Here is the failure.
10/9/2015 8:10:09 PM | 3 | AC Power? | Initialization | 11135 | The task sequence execution engine failed executing an action | -2147024894 | ... loadContentAndVerifyHash ( pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, mapNetworkAccess ), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolveource.cpp,3052) |
It works fine when I test the same TS at my site. I have tried adding these variables, but they did not help.
SMSTSDownloadRetryCount = 5
SMSTSDownloadRetryDelay = 15
Any help would be appreciated. Thanks!
SCCM R2 2012 SP1 "Select a driver" freezes on Driver import for Boot Image
UDI tasksequence setp
SCCM 2012 R2 SP1 - Pre-Provision Bitlocker Windows 7 Cannot Read Drive after reboot
I have a task sequence that was working prior to updating to 2012 R2 SP1 and was working post SP1 until I changed boot images. From 8.1 ADK 6.3.9600.16384 to Windows 10 ADK 10.0.10586.0.
Now, after applying the OS image(Win 7 Ent x64 Sp1), pre-provisioning Bitlocker, and rebooting winload.exe throws an error, 0xc0210000, and says it cannot decrypt the drive. I made sure that the correct partition is getting encrypted. It's set to the OSDisk variable which is the C: drive of the OS image.
I've tried using both the new and old boot images. Both show the same behavior. The task sequence doesn't report a failure just that the OSD is still in progress.
What do I do? Disabling pre-provision and just enabling bitlocker later would add too much time to my image deployment.
Tried creating a new Task Sequence and it is showing the same behavior.
Here's a screenshot of the task sequence in case there is some step I'm missing. I went ahead and disabled bitlocker pre-provisioning and enabling, just so my helpdesk can move forward with imaging. It's mostly a standard MDT task sequence.
Windows 10 Build 1511 XTS AES Cipher strength and BitLocker pre-provisioning
OK, this could well be the very first post on the internet about a potential issue I am looking into. I have a customer that is running SCCM 2012 R2 SP1, want's to look at deploying Windows 10 but is not yet ready/prepared to upgrade the ADK version from 8.1 to 10 on their primary site server (so that they can still ensure existing builds work OK, driver management of the boot image etc.), instead we are going with importing a WinPE image from the Windows 10 ADK (using DISM to first add certain components) and importing that into SCCM worked fine.
However, we started to uncover issues with BitLocker pre-provisioning in that on the first reboot after applying the OS image, the machine would stop and tell us that there are No available recovery options.
I noticed in WinPE that the Encryption type during pre-provisioning was this new "XTS AES 128", instead of the usual "AES 128". If I turned off Bitlocker encryption and decrypted the device, it continued the boot and the remainder of the task sequence.
I undertook some more testing and found that if I imported a Win10 boot image from my own SCCM environment which HAS had the ADK upgraded to Win10 (v10.0.10240.16384), but NOT to the latest ADK now available for download (10.1.10586). This imported boot image still used the "AES 128" cipher strength and the Bitlocker pre-provisioning and reboot worked without issue.
I have still to determine if it is the new WinPE version in the latest Win10 ADK that is the problem (because of the XTS AES) OR if this is a problem related to using an imported Win10 boot image in a non-ADK upgraded SCCM environment.
Just a heads up to watch for this if you upgrade any customer SCCM environments with the latest ADK!
My Personal Blog: http://madluka.wordpress.com
Really slow application install with a new TS
Hello,
Due to me not having the time to invest into MDT, I am working to remove it and revert to the normal task sequencer. The problem is the MDT task installs within 30-45 minutes. The non-MDT task takes that long to get 1 application installed. The non-MDT task seems to do fine until an application needs to be installed. Between the MDT and non-MDT task the only difference is the existence of MDT.
I am sorry, but I don't even know where to begin troubleshooting this one. I looked at the common logs for OSD and client operations and I am not finding any errors. There isn't an issue with hardware between the 2 systems since they are being hosted from a VMWare environment.
Anyone with some direction?
Thanks
PXE working, OSD working, getting ready to enable multicast, looking for suggestions/best-practices...
Guys,
I've been using SCCM USB and ISO boot media (VM's) for the last year while I worked on our Windows 10 image (through all the preview's and issues) and even had our networking team carve out a VLAN in my cube with PXE forwarding to one of my SCCM DP's to test PXE booting as well (so as not to interfere with our existing W7 WDS infrastructure).
It's been a long road with all of the obstacles but now with a mature Windows 10 OSD that lets you pick the OS (Standard or LTSB, x86 or x64) as well as which Office version (2010, 2013 or 2016), and the image now deployed to about 40 IT engineers in our IT area the past few months (along with an SCCM-pushed 1511 upgrade last week), I feel I'm ready for the next step.
That step is to enable dual PXE boot along-side our existing W7 WDS infrastructure for the entire IT data center to begin a wide Beta with me not having to control/aid deployments with boot media. We've already worked out the PXE forwarding to two servers and timing so our WDS answers first, then press F11 to get a menu of PXE hosts, works great and will let us use side-by-side infrastructures.
So now comes enabling multicast on our DP, I'd like to feel like I've crossed the "t's" and dotted the "i's" so what so I need to be aware of? I have requested an IP pool for multicast and teamed the adapter on the DP and set the teams MAC as the PXE NIC, what do I need to do with boot images or WIM's (or even packages?) to ensure they stream multicast versus unicast only? I seem to remember something about settings per boot image or WIM for this? Also, any patches for Windows 2012R2 and SCCM 2012 R2 SP1 I need to have installed for PXE/network issues?
Thanks for any advice offered,
Jack
Configure PXE (WDS Server) to point to a second WDS server (on DIFFERENT subnet).
Hello,
I know I can add the following registry key to our existing WDS server (see below) to present an "F11 menu";
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\Providers\BINLSVC]
"AllowServerSelection"=dword:00000001
...that if pressed, will broadcast for any other WDS servers on the same subnet and present them as menu options to PXE boot from, but what if the other WDS (SCCM DP) is on a different subnet? Our DNS/DHCP infrastructure is not MS, we use Cicso DNS and DHCP and our servers have static IP's (if this matters), we currently use IP helpers to find PXE which we set per location. The goal is to leave our existing WDS infrastructure in-place to serve up our mature Windows 7 image (not created using SCCM or MDT) while still being able to use our SCCM infrastructure for bare metal Windows 10 deployments. I know SCCM can "upgrade" an OS but we're looking at wipe-and-load (party due to McAfee encryption but either way, not upgrading!)...
Thanks for the help,
Jack
let me know steps to add language package to windows 7 operating systems
ADK supports windows 10
PXE will not complete TFTP correctly.
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12/4/2015 10:28:10 AM 3988 (0x0F94) Prioritizing local MP http://xxx.xxx.xxx. SMSPXE 12/4/2015 10:28:10 AM 3988 (0x0F94) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>3d7b4023-fb80-40b1-85be-fb1d5f6c48a3</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CAS20007" OfferIDTime="12/2/2015 10:44:00 AM" PkgID="CAS00018" PackageVersion="" PackagePath="http://SD25-SCCM02.SD25.LAN/SMS_DP_SMSPKG$/CAS0001A" BootImageID="CAS0001A" Mandatory="0"/></ClientIDReply> SMSPXE 12/4/2015 10:28:10 AM 3988 (0x0F94) 00:19:D1:E6:45:83, B25FB435-6C64-DC11-A9F1-000EA629289B: found optional advertisement CAS20007 SMSPXE 12/4/2015 10:28:10 AM 3988 (0x0F94)While running wireshark I notice it get to doing a tftp download of \boot\sources\boot.wim and give a access violation failure. I then get on the screen of the computer that is running the pxe boot, that there is a 0x000001 error and I have a device that failed and I need to restart. I'm at a loss as to what to do here, I know the task sequence works because if I put it on standalone media it installs. I don't know what is going on at this point...
OSD Crash and Burn on Setup Windows and ConfigMgr after R2 Upgrade
Hello Folks -
So I have a Windows 7 image I created with SCCM SP1 Build and capture. I understand that the CM client is part of the build and capture image.
We just recently updated to R2 - so I decided to update the Windows 7 task sequence to install the new SCCM Client package. And it seems to bomb out (Task sequence ends) after trying to install the client. I think there may be a problem where the new client has issues upgrading/uninstalling the old client (on the image) before it can install the new..
Has anyone run into this before?
It certainly is failing on the client.msi install. I can post the logs when I get back to the office.
Thanks -
Diskpart failing to run at task sequence
We are facing issue with diskpart execution team which executes just before format steps. below diskpart.txt is part of pkg.
command is executing diskpart.exe /s diskpart.txt
where diskpart.txt has below command
select disk 0
clean
create part pri
select part 1
Format fs=ntfs quick
however when executing TS its failing. i am suspecting that its happening because package exist in C:\_SMStasksequemce and due to that its not able to perform.
Can someone please suggest solution here ?
Change Computer Name during Windows 10 Upgrade Task Sequence
Hi all,
I know it's an old habit, but we use "-7" or "-8" at the end of our computer names which indicates the client OS version.
now when we upgrade to Windows 10 we want to change the computer name during the OS Deployment task sequence.
no popup needed as we just change from "NAME-7" to "NAME-10". I know how to create a script that will change the computer name and give it the right permissions so it won't fail
my question is - does changing the %OSDComputerName% variable will be enough for the Task Sequence to change the computer name or should I do the change with a script? what is the most acceptable way to achieve this goal without breaking the TS?
thanks,
Tamir Levy
need to configure boot image section in WDS console?
I am trying to capture image windows 8.1 following below blog question i need to use WDS role and need to configure boot image section in WDS console?
https://technet.microsoft.com/en-us/library/dn744290.aspx?f=255&MSPPError=-2147217396
USMT to State Migration Point - OSD - SCCM 2012
Hi Guys,
I'm having an issue with OSD with USMT where for some reason, the user profiles aren't copied back to the new machine once it's been refreshed. I create the standard Task Sequence and elect to use USMT, saving data to the State Migration Point. I run the Task Sequence to capture the user data (this works fine, and I can see the data being stored on the SCCM server), then run through the process of install the new OS. Once this is done and I log in, there's no user data there.
I'm not too sure which logs to be looking at to find out why it's not working. I can barely find anything online related to USMT to State Migration Points.
Powershell using TS Variables
Hello,
i am calling a PS script form a network share during the MDT TS.
$tsenv=New-Object-COMObjectMicrosoft.SMS.TSEnvironment
$group =$tsenv.Value("MDT_SpecialConfig")
when I am proofing the content of $group it is always empty.
If i stop the TS an call the script with comandline, $group has some content.