This particular task sequence started out with the MDT 2013 Toolkit initially after the R2 upgrade and ran into issues with ZTICopyLogs not being able to successfully connect to the logs share. I reverted it back to the MDT 2012 U1 Toolkit, which seemed to resolve that, but now this authentication issue when making the SQL query.
Is it possible to continue to use 2012 U1 with SCCM 2012 R2, or does it need to be the 2013 toolkit? I know with 2013 I ran into issues trying to use it with SCCM 2012 prior to R2. How about the other way around? Thanks, Eric From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Monday, January 19, 2015 2:24 PM To: [email protected] Subject: [MDT-OSD] RE: MDT authentication issue after upgrading to MDT 2013 I suppose that’s possible, but I’ve not done that upgrade (I did a clean install) so I haven’t experienced that myself. Are you sure that you’re using a new MDT toolkit package with your task sequence? Do you have the BDD.LOG? Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Monday, January 19, 2015 11:18 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: MDT authentication issue after upgrading to MDT 2013 The site where I’m running the task sequence is at SCCM 2012 R2 – just upgraded earlier this month. Is it possible that the NAA credentials need to be re-entered? I don’t believe we did that after the upgrade. Thanks, Eric From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Monday, January 19, 2015 1:36 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: MDT authentication issue after upgrading to MDT 2013 MDT 2013 only supports ConfigMgr 2012 R2; MDT 2012 Update 1 supports ConfigMgr 2007 and 2012 RTM/SP1. The symptoms you are seeing are directly related to the differences between ConfigMgr 2012 and 2012 R2. ConfigMgr 2012 uses one network access account, whereas ConfigMgr 2012 R2 can have multiple. That means the credentials are stored differently (using different task sequence variables) between the two. MDT 2013 doesn’t know how to get the values from the original 2012 variables. So you have a few choices: Upgrading to ConfigMgr 2012 R2, downgrade MDT back to MDT 2012 Update 1, or modify the places in the MDT scripts (I believe there are a few of them, but it’s at least ZTIUtility.vbs and ZTIDataAccess.vbs) to understand the old and new variables. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Monday, January 19, 2015 10:04 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] MDT authentication issue after upgrading to MDT 2013 I have an SCCM task sequence with MDT integration that runs a basic process including the MDT gather step. I started seeing a problem after upgrading from MDT 2012 Update 1 to MDT 2013. The problem occurs when MDT gather processes an INI file. The INI includes a SQL query. Nothing in the ini has changed since the MDT upgrade. In the BDD.log I can see the process reading the SQLShare parameter from the ini and attempting the authentication to the share on the SQL server. It sits there indefinitely. I noticed an mshta.exe process running when the client was hung. I killed this process and the MDT gather then progressed. The pertinent log entry in BDD.log is: no credentials were returned from LTICredentials.hta, so no connection is possible. Is there an additional parameter I need to specify in my INI with MDT 2013 in order to prevent it from trying to prompt for credentials? I do not have a SQL ID and password in the INI. The SQL query is hitting the SCCM site server so the network access account of the client already has access. Thanks, Eric Giroux Senior Infrastructure Engineer Unum End User Computing E-mail: [email protected]<mailto:[email protected]> | Office: (207) 575-2482 Mobile: (207) 239-5190 | Fax: (207) 575-2158
