Here's the KB https://support.microsoft.com/kb/2894518
On Tue, Feb 3, 2015 at 2:14 PM, Jason Lang <[email protected]> wrote: > Most likely, this is a result of your apply OSD step installing > update(s) that require multiple reboots. This causes the TS to “break” and > not finish properly, leaving the Client in Provisioning Mode. > > > > The fix is to NOT install these specific updates (there is a list online > somewhere) and/or slipstream these updates into your Reference WIM ahead of > time. > > > > Hope this helps, > > > > *Jason Lang* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *King, Jason > *Sent:* Tuesday, February 3, 2015 9:04 AM > *To:* [email protected] > *Subject:* [mssms] CM 2012 R2 CU2 client in provisioning mode after OSD > > > > Recently, we have started to have a rash of clients that just after OSD > has finished, the clients log in and are perpetually stuck in provisioning > mode. We haven’t had a problem like this in the past but recently we have > seen it start to creep up and be an issue. To Band-Aid the issue we have > removed the apply software updates step from our task sequence which has > seemed to help. Has anyone else had this issue before and figured out what > was causing it? I have seen a lot of posts of people adding reg keys to > the TS to take it out of provisioning mode during the TS but my guess is > that’s not the best way to go about it. > > > > …………………………………………………………………………………………………………….. > > Jason King | Solutions Design Team > > Please consider the environment before printing this email. > > > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This email contains information from the sender > that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise > protected from disclosure. This email is intended for use only by the > person or entity to whom it is addressed. If you are not the intended > recipient, any use, disclosure, copying, distribution, printing, or any > action taken in reliance on the contents of this email, is strictly > prohibited. If you received this email in error, please contact the sending > party by reply email, delete the email from your computer system and shred > any paper copies. > > Note to Patients: There are a number of risks you should consider before > using e-mail to communicate with us. See our Privacy & Security page on > www.henryford.com for more detailed information as well as information > concerning MyChart, our new patient portal. If you do not believe that our > policy gives you the privacy and security protection you need, do not send > e-mail or Internet communications to us. > > > >
