[mdt] Broken MDT again

[jthompson]

I guess the equivalent value for you to use would be MDTDeploy$.

 

Might be worth checking the db permissions. This seems like a reasonable guide to follow for that: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-mdt/use-the-mdt-database-to-stage-windows-10-deployment-information#configure-database-permissions

[garethEds]

Afternoon Everyone,

 

So..... bit the bullet and re-installed MDT on a fresh server. Deployed an image using a copied over task sequence - didn't setup the database part of it all. It worked. Built well. Backed it up.

 

Installed SQLExpress 2022 and it all broke again - no connection to the database.

 

Tearing my hair out with this. Back to the backup......

[jthompson]

So I'm guessing the db permissions article didn't solve it for you, then? It does seem like a credentials/permissions thing.

[PotNoodleTech]

Out of interest - Why are you installing SQL Express over the working system anyway? I've always used the built in click next click next during the install?

[3s-gtech]

Indeed - why are you trying to install a different DB engine?

[garethEds]

Hi - I always followed the instructions from a Johan A book and website where they use a separate database.

 

Always worked for me - except now.

 

G

[MartinT]

Our MDT works fine, even deploying W11. It doesn't need a separate database, the built-in one works fine.

[ITGuyNW]

Never had to install a separate database, seems like extra work

[mavhc]

Hi - I always followed the instructions from a Johan A book and website where they use a separate database.

 

Always worked for me - except now.

 

G

 

Makes the book thicker I guess, or if you're installing 1000 machines every minute

[garethEds]

Our MDT works fine, even deploying W11. It doesn't need a separate database, the built-in one works fine.

 

Hi Martin,

 

If I use the inbuilt one how will I get my data back in from the backup?

 

Gareth

[garethEds]

I'm confused - where do I setup a database in MDT if I am not using an SQL Server? Where are you putting your machine names?

[PotNoodleTech]

Ok I can see where your trouble is i.e you want to restore your old MDT database so you can't use the in built in SQL version and have to install an SQL server but then that breaks MDT?

 

I cant really advise further as have used MDT/WDS in built options for 10+ years so never run into this issue.

[jthompson]

The database is kinda separate in that it's running in an SQL Express instance, but you can install/provision it from within the MDT workbench UI, IIRC.

 

To import details of all our computers from a CSV, I used some PowerShell scripting that's floating around on the web (stuff based on a PowerShell module names MDTDB.psm1).

[MartinT]

If I use the inbuilt one how will I get my data back in from the backup?

 

Different use case - we only build bare metal from MDT.

[3s-gtech]

I thought that you could still connect to the inbuilt DB using SQL Management Studio - so you could push/pull the DB from there.

[garethEds]

Afternoon all - so I've fixed it. A totally random thing but it's fixed.

 

When I entered the FQDN of the SQLExpress server into MDT it would not connect. It could not find it - so has to be DNS yes? This is despite the SQLExpress installation running on the same IP address as the MDT installation. MDT finds the share \\\MDTDeploy without any issues.

 

When connecting to the database, SQL could not find it at all. So I changed the FQDN to the IP Address and hey ho - it connected to SQLExpress straight away. Now why has this happened? It was working fine one day and then not the other. DNS is fine - names/ip addys are all in there.

 

That is for another day - it's working now - so thanks everyone for their input.

 

Gareth