SCCM 2012 R2/MDT 2012 - Deploying Windows 7 UDI CustomSetting.ini setting not applying

I am using an MDT UDI task sequence to deploy Windows 7. The task 'Apply Operating System Image' has the answer file package and unattend.xml file in the correct location.
Within the CustomSetting.ini I have the setting SkipProductKey=YES but, during the deployment it stops on the product key page.
We do not need to input a key since we are using KMS. I did not have this issue in 2007 although I did not use a UDI task sequence. I'm sure I am missing something or it's not using the CustomSetting.ini for some reason or another.

Hi,
Go to http://licensing.microsoft.com. You could download the windows 7 (KMS) Version ISO.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Windows Server 2012 R2 - ALL HF's Failing to install as "Does Not Apply to this computer"

Hi,
A general question about hot fix installs.
I have multiple servers that are all Windows 2012 R2. They do not have internet connections, so I have to install the Hotfixes manually. I download the HF's from the ISO download page (https://support.microsoft.com/en-us/kb/913086) every month. I collect them and install in a bulk install during a release cycle ( a couple times a year). I just realized that NO HF's have installed since JUNE 2014. Every HF that shows up in WindowsServer2012R2 directory fail to install with a message of "The update is not applicable to your computer". Which is fine if that was true, but.... I get this message for every HF from the ISO's since June 2014. NOT one HF thinks it is applicable to my computer. Could that be the case? No HF's apply to my Server 2012 systems since June of 2014?
This is my system info, and below that is the results from attempting to install 95 HF's.
C:\TEMP>systeminfo
Host Name: MYHOST
OS Name: Microsoft Windows Server 2012 R2 Datacenter
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 00252-80025-36226-AA727
Original Install Date: 6/13/2014, 8:04:39 AM
System Boot Time: 3/16/2015, 2:34:45 PM
System Manufacturer: Dell Inc.
System Model: PowerEdge R720
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
[02]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
BIOS Version: Dell Inc. 2.2.2, 1/16/2014
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 262,099 MB
Available Physical Memory: 249,337 MB
Virtual Memory: Max Size: 301,011 MB
Virtual Memory: Available: 288,015 MB
Virtual Memory: In Use: 12,996 MB
Page File Location(s): C:\pagefile.sys
Domain: mydomain.sgn
Logon Server: \\MYHOST
Hotfix(s): 25 Hotfix(s) Installed.
[01]: KB2862152
[02]: KB2868626
[03]: KB2876331
[04]: KB2888505
[05]: KB2892074
[06]: KB2893294
[07]: KB2893984
[08]: KB2898785
[09]: KB2898868
[10]: KB2898871
[11]: KB2900986
[12]: KB2901125
[13]: KB2901128
[14]: KB2909210
[15]: KB2909921
[16]: KB2912390
[17]: KB2916036
[18]: KB2919442
[19]: KB2922229
[20]: KB2923392
[21]: KB2925418
[22]: KB2930275
[23]: KB2931358
[24]: KB2931366
[25]: KB2936068
Network Card(s): 6 NIC(s) Installed.
[01]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: ISCSI
DHCP Enabled: No
IP address(es)
[01]: 192.168.1.30
[02]: fe80::38c9:e59c:5ac2:e0a1
[02]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: NIC3
Status: Hardware not present
[03]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: MGMT
DHCP Enabled: No
IP address(es)
[01]: 7.48.64.32
[02]: 7.48.64.30
[03]: fe80::f14e:9339:9326:c7fd
[04]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 1_swport_VMRepwan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[05]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: NIC2
Status: Hardware not present
[06]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 2_swport_VMOpswan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.
I have a script that runs each HF install.. If I run them manually without the tool I get the same results so it is not the script..
Installing 95 patches
for Microsoft Windows Server 2012 R2 Datacenter x64
Repository path: U:\Patch Repository_4_1\2012_R2_HFs\
1. Windows8.1-KB2894852-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
2. Windows8.1-KB2894856-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
3. Windows8.1-KB2920189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
4. Windows8.1-KB2926765-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
5. Windows8.1-KB2928120-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
6. Windows8.1-KB2931358-x64.msu patch status: ALREADY INSTALLED - SKIPPING
7. Windows8.1-KB2931366-x64.msu patch status: ALREADY INSTALLED - SKIPPING
8. Windows8.1-KB2933826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
9. Windows8.1-KB2939576-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
10. Windows8.1-KB2953522-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
11. Windows8.1-KB2957151-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
12. Windows8.1-KB2957189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
13. Windows8.1-KB2957689-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
14. Windows8.1-KB2961072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
15. Windows8.1-KB2961887-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
16. Windows8.1-KB2962872-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
17. Windows8.1-KB2964718-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
18. Windows8.1-KB2964736-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
19. Windows8.1-KB2965788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
20. Windows8.1-KB2966072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
21. Windows8.1-KB2966826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
22. Windows8.1-KB2966828-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
23. Windows8.1-KB2971850-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
24. Windows8.1-KB2972213-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
25. Windows8.1-KB2972280-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
26. Windows8.1-KB2973114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
27. Windows8.1-KB2973201-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
28. Windows8.1-KB2973351-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
29. Windows8.1-KB2974008-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
30. Windows8.1-KB2976627-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
31. Windows8.1-KB2976897-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
32. Windows8.1-KB2977292-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
33. Windows8.1-KB2977629-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
34. Windows8.1-KB2978668-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
35. Windows8.1-KB2982794-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
36. Windows8.1-KB2982998-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
37. Windows8.1-KB2987107-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
38. Windows8.1-KB2987114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
39. Windows8.1-KB2988948-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
40. Windows8.1-KB2992611-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
41. Windows8.1-KB2993651-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
42. Windows8.1-KB2993958-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
43. Windows8.1-KB3000061-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
44. Windows8.1-KB3000483-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
45. Windows8.1-KB3000869-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
46. Windows8.1-KB3001237-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
47. Windows8.1-KB3002657-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
48. Windows8.1-KB3002885-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
49. Windows8.1-KB3003057-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
50. Windows8.1-KB3003381-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
51. Windows8.1-KB3003743-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
52. Windows8.1-KB3004150-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
53. Windows8.1-KB3004361-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
54. Windows8.1-KB3004365-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
55. Windows8.1-KB3005607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
56. Windows8.1-KB3006226-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
57. Windows8.1-KB3008923-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
58. Windows8.1-KB3008925-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
59. Windows8.1-KB3010788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
60. Windows8.1-KB3011780-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
61. Windows8.1-KB3013126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
62. Windows8.1-KB3013455-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
63. Windows8.1-KB3014029-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
64. Windows8.1-KB3018943-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
65. Windows8.1-KB3019215-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
66. Windows8.1-KB3019978-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
67. Windows8.1-KB3020393-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
68. Windows8.1-KB3021674-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
69. Windows8.1-KB3021952-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
70. Windows8.1-KB3023607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
71. Windows8.1-KB3036197-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
72. Windows8.1-KB3021953-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
73. Windows8.1-KB3022777-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
74. Windows8.1-KB3023266-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
75. Windows8.1-KB3023562-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
76. Windows8.1-KB3024663-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
77. Windows8.1-KB3029944-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
78. Windows8.1-KB3030377-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
79. Windows8.1-KB3031432-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
80. Windows8.1-KB3032323-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
81. Windows8.1-KB3032359-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
82. Windows8.1-KB3040335-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
83. Windows8.1-KB3033408-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
84. Windows8.1-KB3033889-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
85. Windows8.1-KB3034196-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
86. Windows8.1-KB3034344-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
87. Windows8.1-KB3035017-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
88. Windows8.1-KB3035034-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
89. Windows8.1-KB3035126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
90. Windows8.1-KB3035131-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
91. Windows8.1-KB3035132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
92. Windows8.1-KB3037634-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
93. Windows8.1-KB3039066-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
94. Windows8.1-KB3044132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
95. Windows8.1-KB3046049-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
Thanks,
Dave

Hi Dave,
Would you please check CBS lg file and other relevant event logs if find more clues? On current situation, please refer to following article and check if can help you.
Update is not applicable to your computer- but it is
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows 2008 R2 group policy not applied to windows 8 Workstations, but applied to XP and Win 7

I have a Windows 2008 R2 Domain Controllers and have a Policy to put a specify wallpaper, eventuality i have to change the Wallpaper, this setting applied sucesfully in Windows xp and Windows 7 workstations, but not applied in Windows 8 workstations even
if i run gpupdate /forcé,
Best Regards,
Thank you

Hi,
Thanks for posting in the forum.
Before going further, would you please let me know how did you configure the Group Policy setting to deploy the wallpaper? Have you configured some settings to limit the scope the GPO applying?
If all Windows 8 machines failed to receive the GPO settings? In order to narrow down the cause of the issue, I suggest we could try to collect the following information for troubleshooting.
GPMC.log
==================
a. On domain controller, click Start ->Run, type GPMC.MSC, it will load the GPMC console.
b. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper
user in the wizard)
c. Right click
the resulting group policy result and click the "Save Report…" => save report to save the report to a HTML file.
Once we get the report, please check if the settings have been applied to the target correctly.
In addition, would you please let me know whether you have imported the latest Windows 8 Administrative Templates to the Windows Server 2008 DC? If not, please try to download and import it.
Then try to configure the wallpaper GPO settings again to see if it could help.
For details, please refer to the following articles.
Administrative Templates (.admx) for Windows 8 and Windows Server 2012
http://www.microsoft.com/en-us/download/details.aspx?id=36991
Set Desktop Background via Group Policy in Windows 7, Windows 8 in a Server 2008 or Server 2012 Domain
http://dizzyit.com/2013/04/14/set-desktop-background-group-policy-windows-7-windows-8-server-2008-server-2012-domain/
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Windows 8.1 - Security policies not applying

Hi All,
I'm having a bit of an issue with group policy settings not applying on Windows 8.1. Most of the policies are applying as they should but for some
reason certain security settings (Password policy, Account lockout policy, Interactive logon message etc.) are not.
I can see from GPResult that the policy is not filtered out and can confirm that some of the settings from the policy are getting applied!
FYI: The DC is WS2003 and we have not imported the Windows 8.1 ADMX templates... Could that be causing the issue?
Any help you guys might be able offer would be greatly appreciated!

As I know, Security policy like Password policy, Account lockout policy, Interactive logon message should work even the DC is Win Server 2003.
I suggest you check whether these policy are overridden by other GPOs due to the the GPO Priority, you can find detailed information in this link
Group Policy processing and precedence
http://technet.microsoft.com/en-us/library/cc785665(v=ws.10).aspx
Yolanda Zhu
TechNet Community Support

SCCM 2012 - How can I deploy Windows 7 to ANY computers when booted via NIC?

Here are the things that I would like to happen.
1. I should be able to have ANY laptops or desktops boot via network, then see the Windows 7 task sequence select and install the OS, drivers, programs. The computer name should all be "TEST" and not joined to the domain.
P.S
The reason why is because I don't want to have to know the MAC address of the computer every single time I deploy a task sequence.
Thanks for any input.

Hi,
Create your task sequence and deploy it to the special 'Unknown Computer' objects.
I personally use a collection named 'Imaging Systems' and added the 'x64 Unknown Computer' and 'x86 Unknown Computer' objects there. All my task sequences are set as available and deployed to that collection, so I can choose whatever task sequence I need
when I PXE boot a new machine.
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

SCCM OSD and MDT 2012 - Task Sequence query

Hi All
I have single server SCCM 2012 R2 server with MDT 2013 successfully integrated. I'm looking to create a 'Sysprep and Capture' type Task Sequence within SCCM, so that this can be done via PXE rather than SCCM's more manual 'Capture Media' method. Just
wondering if anyone has thoughts on this, experience, pointers etc?
Couple of options that look possible are:
MDT Toolkit Package - include in SCCM based Task Sequence. Would it then be fairly easy to mimic ts steps detailed in MDT's existing 'Sysprep and Capture' TS, but within SCCM?
SCCM TS Steps - I've seen there are a number of TS Steps that look like they may enable OS Capture, but if so, bit confused there isn't more documented \ blogged on this kind of TS, would have thought this was a common requirement for a
SCCM TS? (TS Steps of interest within SCCM: 'Prepare Windows for Capture' and 'Capture Operating System Image')
Any assistance much appreciated!
Kind Regards
Andrew

There is a bit of debate about the best way to capture reference images. Check out this good blog that reviews the options:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/163/The-battle-begins-Building-the-perfect-reference-image-for-ConfigMgr-2012.aspx
Having said that, you can certainly create a capture task sequence in SCCM. If you choose to create a new task sequence,you should see a build and capture option. Simply create a build and capture task sequence and then remove the build steps.
You will be left with:
I've used this method in certain cases.
Or as you said, if you are integrated with MDT, you can create an MDT task sequence to do the capture or add MDT steps as needed.
Hopefully that helps!
Jeff

SCCM 2007 with MDT 2012 Update 1 - LTI Build Process - "UserLocale" setting is all lowercase.

Greetings all. I'm trying to resolve a situation where the "UserLocale" property is being set to "en-us" opposed to "en-US". Quick environment stats: SCCM 2007, MDT2010, using LTI build process with a
custom UDI. 2 Build Sites (customer build sites), both sites have branch distribution points.
Both sites are performing the exact same LTI builds. Same task sequence.
Both sites have MDT location records that have the "UserLocale" property defined as "en-US".
Both sites successfully build the same LTI build, but post build; Site A has correct UserLocale entry of "en-US", while Site B does not have correct UserLocale entry - it is set to "en-us". This wouldn't normally be a big
deal, however we have an enterprise application that is hard coded to look for case specific property of "en-US", so this application does not function as desired as Site B.
Both builds use the same task sequence, same OS.WIM (Windows 7 x86), and same unattend.xml. The unattend.xml does have UserLocale specified as "en-US" (and also the MDT location records for Site A and Site B both have "UserLocale"
property defined as "en-US", so I do not understand where the lowercase "en-us" is being populated from during the client build for Site B, when it works correctly for Site A?
Bdd.log for client build at Site A shows:
Obtained USERLOCALE value from SQL: USERLOCALE = en-USUpdated
C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-US (value was en-US)
Property USERLOCALE is now = en-US
Bdd.log for client build at Site B shows:
Obtained USERLOCALE value from SQL: USERLOCALE = en-US
Property UserLocale_Edit is now = en-us;0409
Property UserLocale is now = en-us
Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
Updated C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-us (value was en-US)
Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
Can anyone offer insight as to my next troubleshooting steps? I'm not sure why Site B, bdd.log - unattend.xml shows updating UserLocale to en-us instead of en-US?
(Please note I have verified that the OS.WIM, unattend.xml, and all MDT scripts that run during task sequence execution are exact matches on the BDP's for each site. Same size, date, and content)

Well, there must be something that is different... If you zip up the logs (all of them) from each setup, and mail them to me, I can take a quick look.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 7 x64 SP1 updates not applied to image

I am having a very strange issue. After working correctly for over a year, my build and capture Windows 7 x 64 SP1 task sequence is not working. The first part of the problem is that the image will not capture on a SCVMM 2012 R2 cluster. That problem
has been mentioned in a different post and I have a call into MS.
The second issue is strange. I used my normal install.wim that had updates injected into it via SCCM offline updates. When I built the computer, it showed all updates as being needed including SP1. This same install.wim had worked perfectly
prior 9/15/14. I then did a build using just the install.wim that came with the Windows 7 SP1 iso, I had the same problem. When I go into the computer properties, it shows Windows 7 Service Pack 1 as the OS. However, if I go to Windows Updates,
it shows that SP1 is needed. I apply the update it takes about 3 minutes and it is installed.
Has anyone experienced this issue? The only major changes in the environment was moving the build and capture machine to a SCVMM 2012 R2 infrastructure that is built on Windows 2012 R2 OS. Prior to that we were using SCVMM 2008 R2 on Windows
2008 R2 OS.

Hi,
I think you are running same problem as described in the following article:
http://support2.microsoft.com/kb/2894518
Updates trigger multiple boot is caused TS failing.

Windows 2008 R2 group policy not applied on some of the computers

Dear All,
I have windows 2008 r2 as domain controller and configured group policy. when I am changing existing group policy most of the computers not affecting with update policy.
is there any server or any other method required to configure?
every time i need to update group policy manually on computers.
pls help
SUNIL PATEL SYSTEM ADMINISTRATOR

You have an issue with AD DS replication.Ensure all domain controllers are in sync

MDT 2012 - Failure 9701: Unable to find any version of USMT, unable to perform user state migration. Failed to run the action Restore User State. DNS Record does not exist. (Error: 000025E5; Source: Windows)

I am having trouble trying to capture a new Windows 8 image with WDT 2012.
My Setup -
Server 2012
WDS
MDT 2012
Windows 8 ADK
Hyper-V
I have created a new task and I can get the image to successfully deploy the image to a VM but it seems to fail at the Restore User State task.
Once the install Applications task has finished I added a Suspend task so I could customize the image a little. Upon resuming the task sequence is where the above failure message appears. I can see it gets to the next step (which is 'Restore User State')
but that seems to be where is crashes.
Does anyone have any advice on what I might be doing wrong or what I can do to resolve the above issue?

WAIK being installed was probably your issue so I wouldn't bother disabling the restore task. It is used to migrate user data, docs, and settings on refreshes, not new builds. It doesn't affect CopyProfile, just note that data will be migrated on refreshes so
some aspects may change, ie wallpaper, shortcuts, etc but what gets migrated with USMT can also be configured.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Windows Server 2012 GPO setting are not apply on windows Xp clients

Hi
I am create GPO on windows server 2012. 300 clients on domain are working fine, GPO setting apply on all windows 7, 8 clients. But 200 clients of windows XP are not working. GPO setting are not applies on XP. I am trying to Group Policy
Preference Client Side Extensions for Windows XP (KB943729) on one window XP client, all GPO servers 2012 setting is working fine. But is not solution. I have 200 clients of windows XP, Please provide batter solution on one click command and apply all 200
XP clients.
Thanks.

Dear,
I have Windows server 2012 , i have install ADDS with Forest functional level 2008 & Domain functional level 2008 .
I have applied GPO to particular OU, when i login to domain user on Windows 7 PC all GPO working fine but when i login on Windows Xp SP3 PC its not applied on XP.
I am facing issue on windows XP clients it is true. Please see this URL address:
http://blogs.technet.com/b/grouppolicy/archive/2009/03/27/group-policy-preferences-not-applying-on-some-clients-client-side-extension-xmllite.aspx
Please provide batter solution on one click command
Thanks.

Deploying Windows 8.1 on Mac Pro's Late 2013 model

Hi!
I am trying to figure out how to use MDT to deploy Windows 8.1 on the new trashcan Mac Pro's.
This is what I've done so far.
Disabled the default Format and partiton step with the property DONOTFORMATANDPARTITION=YES just to get rid of errors at the end, i have alos tried to remove the Volume entries in this step with out the above mentioned property.
In this step i have also set the Disk type to GPT and checked the Create Extra 'Active' Partition
Created a custom answer file to diskpart with the following command
sel dis 0
sel par 4
format fs=ntfs quick override
active
exit
Running my custom diskpart step after the default one.
Changed the default Install Operating System step to install on disk 0 partition 4.
All seems to work fine until the computer reboots and i should start windows to continue with the deploy.
Instead of booting windows it boots into OSX.
I've tried to change the start disk with the OS utility, but it gives the error "The bless tool was unable to set the current boot disk."
Ive tried the exact same thing on a older Macbook Pro, and this works flawless. It seems that Apple dropped some legacy support in the new EFI firmware on the new Mac Pro.
If i try to use bless with the --legacy parameter it tells me "Legacy mode is not supported on this system". I used legacy to boot windows on the older Macbook Pro.
Anyone got this working or have any suggestions?

Solved it!
It's not nice, but hey it works.
Here is how i did it.
I scrapped the idea of using any form of script (Applescript) or other custom stuff.
Instead I just fooled Boot Camp Assistant to think inserted a "BootCamped" USB even tough I inserted the LiteTouchPE_x64 based USB. The only files/folders Boot Camp Assistant looks for seems to be.
$WinPEDriver$
BootCamp
BootCamp\BootCamp.xml
setup.exe
autorun.inf
So just create the folders $WinPEDriver$, BootCamp
Create an empty BootCamp.xml file inside the folder BootCamp
copy setup.exe from the Windows media. (Might work with an empty txt file renamed, havent tested)
copy autorun.inf from the Windows media. (Might work with an empty txt file renamed, havent tested)
Start Boot Camp Assistant, uncheck the first 2 boxes and leave the one about creating a partiton.
Desiced on the BootCamp partition size.
And then next next finish :)

Deploy Windows 8 To Go through SCCM 2012 SP1

First a little backgroud:
I have SCCM 2012 SP1 with MDT 2012 Update 1 integrated. I am using an MDT UDI task sequence to deploy windows 8 and it works perfectly. My Windows 8 image is fairly thin (only containing OS updates and C++ runtimes), and I am using the MDT database
and an MDT task sequence in SCCM 2012 to dynamically set a list of SCCM Applications to install as well as settings based on location.
Now I want to get Windows To Go provisioning working in SCCM 2012 SP1. I had a powershell script that preparied the drive and applied a thick image (including office and other apps) to it then updated unattend.xml with a computer name and the domain join
info. That worked for me however I'd like to levarage the dynamic task sequence that I described above to build these To Go sticks the same as my other Windows 8 machines without having to keep updating the thick image evertime something changes.
There isn't much info out there that Iv'e found on setting up SCCM 2012 SP1 to provision windows to go here are the two that I have found
http://ixrv.blogspot.com/2012/10/provisioning-windows-8-to-go-with.html
http://technet.microsoft.com/en-us/library/jj651035.aspx
I followed the instructions in the first link and was able to run the Windows to Go Creator program and apply the prestaged wim to the USB stick. I rebooted from the USB stick Windows PE started and started to run my task sequence then it errored out on
the apply image step. At this point it occured to me that the MDT SCCM task sequence was probably not setup for prestaged media and or Windows To Go.
So my question is am I on the right track? Do I just need to examine each step in my task sequence and make sure that it will work properly with my Prestaged/Windows To Go stick? If so has anyone actually gotten this to work that could give me some advice?
Or is it asking too much to have a dynamic Windows To Go task sequence and I should just be building a thick image and using a second task sequence specifically for Windows to go?
are there any other resources for Windows To Go with SCCM that I'm missing?
Thanks,
Tony

First of all sorry I missed your last three posts I have to check my email notifications. I'll try to answer all of them even though I think the last part is the only one where you are still stuck.
When I created my prestaged media I didn't put anything into it except for the the OS image and my PE image. On the Select Application and Select Package screen in the prestaged media wizard remove any application or packages that are added automatically.
The task sequence is supposed to be smart enough to know if the version of the package that is on the prestaged media is out of date and go to a DP to get it but that didnt work for me. The only way I was able to get it to work was to remove all the packages
from the prestaged media even the Customsettings package, the MDT toolkit package, USMT, etc..
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d729d0ff-829f-4af8-91af-2131b3355fd0/
This thread which is about prestaged media in SCCM 2007 helped me to understand how prestaged media is supposed to work. Basically what I learned is that once the computer is rebooted from the ToGo stick into PE the task sequence will run the same as any
other task sequence installing any applications and setting up your ToGo stick just like any other computer that runs the task sequence they dont need to be in your prestaged media for this to happen.
You shouldn't need to worry about partitioning WTGCreator.exe will partition the ToGo stick for you I'm just using the standard MDT Integrated partitioning in my task sequence. The one thing that I did was set the Windows To Go Creator package to "run from
distribution point" which speed things up because then it didnt download the prestaged wim then apply it to the USB drive.
Is it booting into PE then rebooting? Did you check the "Allow unattend operating system deployment" check box when you made your prestaged media? If so it wants you to have set the task sequence to run in a task sequence variable SMSTSPreferredAdvertID
to the task sequence ID you want to run. I'd just remake the media and leave that box unchecked.
Good luck and let me know how it works for you. I'll check back sooner this time I promise.

SCCM 2012 MDT 2012 UDI Require domain credentials to run task sequence

We are in the process of moving to SCCM 2012 integrated with MDT 2012 for OSD from using MDT 2012 by itself. We're trying out UDI task sequences and have noticed a pretty gaping hole in functionality vs MDT 2012 by itself: password protecting a task sequence.
In MDT 2012 there was a built-in feature that required domain credentials to run a task sequence. If one exists using SCCM/MDT 2012, I haven't been able to find it. I've only found stuff like this http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ which
would allow you to set a password, but not authenticate against AD. So, I'm wondering if there are any options to protecting a task sequence with domain authentication?
My understanding is that the Refresh and Replace StageGroup only run when you kick off a UDI task sequence in Windows. That means I have to make a task sequence available to the Configuration Manager Client in order for a tech to run a Refresh/Replace. And,
that in turn means that the UDI task sequence will be visible to all users since it needs to be available to their computer. Or, am I completely missing how UDI OSD should flow? If so, then I hope someone can correct me.
I'd appreciate any help or advice you can give. Thanks.

Hi,
I am sorry to say that you are correct in your conclusions. There is no builtin way in ConfigMgr/MDT/UDI to require a domain username/password to run a task sequence, your option from Windows-noob.com is one way of solving it.
Regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec
Thanks for the info. What about workflow? How do you usually handle UDI in Replace and Refresh scenarios? Do you deploy the task sequence to collections that users can access?

SCCM 2012 R2/MDT 2012 - Deploying Windows 7 UDI CustomSetting.ini setting not applying

Similar Messages

Maybe you are looking for