Aburns2

What we do at my organization is we use the most recent version of MDT with the Windows 10 ADK to capture the Windows 10 .wim file, and then import that into SCCM. We've patched SCCM to version 2012 R2 with SP1 and updated all of our boot images to WinPe 10. In fact, that is my personal recommendation for SCCM environments regardless of the OS, capture with MDT and deploy/manage with SCCM.

For OSD, the easiest way I would imagine is to use "copyprofile=true" in the unattend.xml file to create a new default profile based on changes made to the local Administrator account during the creation of your image.

Here's the long and the short of it. The licenses for using SCCM on an endpoint (a client computer that is not a server) are included as part of the core CAL and enterprise CAL suites. These licenses are called client management licenses. My understanding is that this is part of the volume license agreement with Microsoft. As someone has already mentioned, you should be on the phone with your reseller or TAM confirming licenses. A server management license is something different. They are not included in the CAL suites, and are more expensive. They are required for every server (whether physical or virtual) you manage with SCCM, if you decide to manage servers with SCCM. The SCCM management software itself comes with a product key that will activate the software. It will also come with a product key to SQL Standard for using very strictly with SCCM.

Update: Well, calling Microsoft on this issue is turning into a waste of time. After being transferred about twelve times, I was told that "Windows 10 imaging" is not supported before being hung up on. Microsoft support is turning out to be rather useless.

Currently my organization is very heavily looking at deploying Windows 10 to our environment. We are a school, and thus we have a lot of public access labs that are currently running Windows 8.1. A major, major complaint that we've received is the time that it takes for a user to log in the first time they log into a computer. We've noticed that the first log in time with Windows 10 in a test environment was even worse than it was on 8.1. So, here's my question. Before we deploy Windows 10 to our labs, is there a good way other than hacking the default profile to reduce the time it takes to log into a computer for the first time? PS: I did try to call Microsoft on this and got nothing but the run-around.

Without a log file, there's not much anyone here can do to really help. A log can be found in X:\Windows\Temp while booted in the SCCM boot media (I'm assuming you're running SCCM). Now, I myself have personally run into an issue when trying to stage WinPE through something else other than PXE or a usb thumb stick, and that is where SCCM throws that exact message when deploying the task sequence to a computer will full disk encryption, such as bitlocker or another third party product such as Sophos. Formatting the drive before hand solves the issue. I can't say if this is the same issue that you're having, at least not without a log file.

Administration -> Site Configuration -> Sites -> Right click on your site -> Properties -> Publishing Tab.

Here's one idea. You could try turning system discovery off, and then try deploying the SCCM client through group policy targeting your OU instead of using client push. Successful client installs should show in the console even with discovery off. EDIT: Just make sure the AD schema is extended and the site is published to AD.

Hello all. Currently my organization just started a phased project of upgrading about 1200 computers with Office 2010 to Office 2013. We're doing this a building at a time, which equates to about 50 - 100 computers per week, depending on the size of the building. It's mostly going well. The only real issue so far has been with two specific computers, both of which are reporting back "CI Version Info Timed out." One of our help desk technicians visited one of the computers and noticed in software center that the application deployment never showed and that it appears like the computer is not picking up a policy. Checking the "ccmcache" folder revealed the Office installation files was never downloaded from the distribution point. We did try reinstalling the sccm client, both through the "install client" in the context menu in the console and through the right click tools, neither one resolved the issue. Checking the log files doesn't reveal much. The thing that I can find out of place in the log files is an error message that says "GetInstanceFromLantern failed (0x80041002)" in the CIStore.log. Any ideas?

This is from your log file: Failed to run the action: Disable Flash Update. Logon failure: unknown user name or bad password. (Error: 8007052E; Source: Windows) TSManager 10/8/2014 4:03:01 PM 356 (0x0164) Now I don't know how your task sequence is set up. Is this action set up to only run specifically for the 7010? The other question I have is the task sequence installing the drivers for the 7010? Are there any missing device drivers when you pull up the device manager on the 7010 after a failed OSD attempt? Also, do you have what's called a Network Access Account setup on the SCCM site?

1) You need to have the Software Update role installed on one of your site servers. I will usually put this on the Management Point. 2) You need to perform an Update Synchronization on your site. This is done by going to Software Library -> Software Updates -> All Software Updates then click on "Synchronize Software Updates" at the top of the screen. This can also be done automatically on a schedule through the site settings. If this is a new server setup, you need to do a manual sync just to get it started. 3) You need to download the updates as a package to your site server. This is done by selecting the updates, right-clicking on the updates, and then clicking on "download." The prompts will have you create an update package that you'll need to throw onto your distribution point. 4) You need to schedule an update to the Windows 7 image. This is done by going to Software Library -> Operating Systems -> Operating System Images and then click on the image and then clicking on "Schedule Updates." 5) Alternately, you can also push the updates out to existing clients by creating an update group and an automatic deployment rule.

Currently we are planning a project to roll out Office 2013 to our current environment, which is currently running almost homogeneous Office 2010. The issue we is that we have a mixed environment of 32 bit and 64 bit Office installs. The way I'm planning to do this is through the supersedence feature in SCCM 2012 r2 with cu1. My question is rather simple. If I specify a supersedence relationship in SCCM, will SCCM replace all copies of Office 2010 across the site regardless of collections and current deployments? Or will SCCM limit the upgrades to solely those collections that have the Office 2010 application deployed to them? The reason I'm asking is because 1) I would like to test the deployment in a test collection and 2) I have select collections that have to remain on Office 2010. Thank you.