yesterday I upgraded my environment to the final MDT 2013 update 1 (sccm is on 2012 R2 SP1 with CU1)

since then when I want to use an mdt integrated task sequence with UDI, it halts in the page new computer details with the warning 'username format is invalid' like you can see here:

so it scrambled the username into some weird value.

this is happening when i reuse the existing UDI TS (but with the updated mdt toolkit and settings packages)

so also reusing the customsettings.ini where I specified the OSDjoinaccount (domainname\username) and OSDJoinPassword (containing the pw in cleartext) and reusing the modified config.xml from the other mdt package

then I tried with a newly generated config.xml and have the same issue.

this worked fine with the mdt 2013 update 1 beta, which I uninstalled, removed integration, installed mdt 2013u1 final, integrated again, generated a new dummy mdt TS to create the new packages

anyone who noticed this also?

Update: just tested with a new clean MDT UDI ts: same behavior!

• Edited by grundlichkeit Wednesday, August 19, 2015 10:46 AM

I have the exact same issue.

Tried to file a bugreport on connect, but the site is slow and the forms are just timing out.

Regards
Trond

• Edited by Trond Karstensen Wednesday, August 19, 2015 6:13 PM

When going to the connect page, I get page cannot be found.  Anyone else getting that when going to the connect link?

I'm getting the same results with the OSDJoin 

When going to the connect page, I get page cannot be found.  Anyone else getting that when going to the connect link?

I'm getting the same results with the OSDJoin 

Connect link works for me. Do you have an account with Connect to provide feedback?

Honestly I dont know, it shows me logged in at the top when I go to the site, so I would assume so??

I've just updated connect with a 'workaround'. It works when adding the same variables as TS variables directly in the Task Sequence just before the UDI Wizard starts.

Trond

what happens if you use the domain join directly from the SCCM TS?

what happens if you use the domain join directly from the SCCM TS?

It does not make a difference. You are unable to complete the UDI Wizard, because it needs the username & password fields to be completed.

Hi Guys,

I've fixed this problem (or at least worked around it) by passing the username and password as Task Sequence variables. So add a couple of steps to your Task Sequence to set each variable instead of using customsettings.ini

I've also found that you need to fully qualify your domain name now.

So instead of just domain\username you now need you specify your FQDN i.e. domain.com\username

If anyone needs additional screen grabs etc let me know.

Update: I've just noticed that Trond posted a similar workaround, sorry for doubling up on that one.

Cheers

Damon

• Edited by Damon A. Johns 23 hours 30 minutes ago

So I did two new task sequence variables.  Called the variable OSDJoin and OSDPass. I referenced them in the UDI as %OSDJoin% and %OSDPass%

I fully qualified the domain name, I've always done that anyway.  Do I need to add quotations or anything?  It's still not accepting the credentials.

I've just updated connect with a 'workaround'. It works when adding the same variables as TS variables directly in the Task Sequence just before the UDI Wizard starts.

Trond

For the variables to work in the customsettings.ini, you would have to define them as they are not MDT based variables and not known to ztigather.  

Nevermind.....redid the task sequence variables to match what's in the customsettings.ini and works like a charm now.