Hi,

SCCM 2012 R1 cu1 OSD with MDT. The MDT have two deployment shares. How to handle Network Access Account?

Or I find an interesting issue!?

We do OSD/MDT deployment for the Windows Clients, It works fine. I have one Network Access Account.

Now we would like to do our Server Deployments also with SCCM OSD/MDT. I thought I was perfect to use another MDT share and MDT-DB for servers and with an Network Access Account that is limited for the MDT server parts. And it works fine MDT role you name it.

But we notice an issue it brakes the Windows Client OSD installation with..

ZTIGather.log
ZTI I error opening SQL connection: cannot open database "MDTDB" requested by the login The login failed (-2147467259)

I notice the OSD starts to use the new server NAA, hum. I could not get this to work again, so I created a new NAA for the client installation. And wolla!! the OSD/MDT client installation starts works again.

But the downsides is that it brake the OSD/MDT server installation

zti error opening SQL connection: cannot open database "MDTDB" requested by the login The login failed (-2147467259)

 Is there something wrong

Are the DBs for each type on the same SQL instance?

If so, why are you using two different shares? The share specified in customsettings.ini for a ConfigMgr task sequence is purely for setting up a secure connection to SQL Server and has nothing to do with accessing any MDT functionality or the MDT deployment share -- the MDT deployment share is not used at all for ConfigMgr TSes -- that's what the MDT Toolkit and settings packages are for.

Hi,

Are the DBs for each type on the same SQL instance?
-Yes

If so, why are you using two different shares?
-Thats a good question, and I dont know. The first share was made by an consultant, the second did I. I have always configured the settings in the MDT Toolkit and settings packages, and have not been sure whar the mdt share is used for.

To fix this:

-I create just an SQLShare for secure connection to SQL Server.

- I also see that it is unnecessary to have two NAA, It dont secure anything. SCCM test all NAA any way, so there is no point to separate the client and server installation.

Correct?