MDT 2010 - OSDComputerName not being applied from Database
-
24 Januari 2012 16:10
I've just setup MDT 2010 and got litetouch installs working nicely and I am expanding this to set the computername based on the mac/serial of the computer using the MDT database.
Everything appears to be setup and working ok apart from the computer name isnt being set to what it should be. Looking through the BDD.log file the database is being queried ok, and returns the correct result including the new computername but this never gets applied because the computer name has already been set to the auto-generated MININT-xxxxx format.
I've been following this guide and up till now it has all worked a charm however I'm stumped on this so any help would be appreciated
Here is the top of my customsettings.ini:
[Settings] Priority=CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins, Default Properties=MyCustomProperty [Default] OSInstall=YES SkipWizard=YES SkipFinalSummary=YES SkipComputerName=YES DeploymentType=NEWCOMPUTER JoinDomain=DOMAIN DomainAdmin=Admin3 DomainAdminDomain=DOMAIN DomainAdminPassword=PASSWORD KeyboardLocale=en-GB UserLocale=en-GB UILanguage=en-GB TaskSequenceID=Win7Test1 TimeZoneName=GMT Standard Time WSUSServer=http://GS01:8530 [CSettings] SQLServer=GS01 Instance=SQLEXPRESS Database=MDT Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerSettings Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR
Semua Balasan
-
25 Januari 2012 5:58is sql and MDT on the same box?
-
25 Januari 2012 9:03Yes, they are both on the same box, the client has no issues connecting to and successfully querying the database, the problem is when it tries to apply the OSDComputerName value retrieved from the database it fails to apply it because the computername has already been automatically set to MININT-<random value>.
-
29 Mei 2012 11:02
Hi,
Did you ever get this problem resolved, i am having the exact same issues as you describe. I have set the OSDComputerName value just like you, it applies the MININT-XXXX computer value.
Steve
- Diedit oleh Steve Mills 29 Mei 2012 11:07
-
29 Mei 2012 11:14
Yes and no, it only seemed to cause problems for this one PC, when I used the same process for a different machine it worked fine and correctly assigned the right computer name from the database.
The only thing I can think that might have caused it was initially I was trying to assign the computer name based on the MAC address of the machine, I have since changed to using the Serial Number instead as this seems more reliable (and easier to find on new machines!), I've no idea how this happened or even if this was somehow causing the problem but its the only thing I can think of.
My only suggestion would be to try with a new PC that hasn't been anywhere near your MDT system yet and if possible try using just the serial number to set the computer name and you might get lucky and have it work like I did.
-
29 Mei 2012 12:04
Yeah I tried serial number first, then MAC, neither of which worked, then i looked at the log files and realised it wasnt connecting to SQL because it was trying to connect as anonymous (i am not yet sure if i have resolved that as i am just performing a deployment right now as i speak to test, so thanks for such a prompt reply). I have switched to using named pipes as well now as ive read that's the best way of doing it.
can i ask another question?
Deployment Shares - do you use multiple ones or just one for everything? I am failing to see how i can efficiently use only one deployment to perform reference system builds, new builds, installing this app and that app, surely it would involve keep editing the custom settings.ini file to change what task sequence runs, am i missing something here or should i be using multiple shares? how have you done it?
thanks
Steve
-
29 Mei 2012 13:41
I would recommend at least 2 Deployment Shares. One for Lab/Reference image generation and one for the production environment. I would also separate Client and Server deployments.
Regards
Maik
-
29 Mei 2012 13:49
We use just the one share here and i just update the settings.ini when doing a reference system to update the image. If you are installing different apps that you need to enable and disable it might be worth looking at installing them via extra steps in your task sequence that you can enable and disable as needed, or you can use the database to set different packages to install based on MAC/Serial just like setting the computer name, I use the Make and Models feature to install certain drivers during the post install phase for models that need them (stupid AMD video drivers).
So while you can go through and setup multiple shares it might not be needed, and if you did then its a lot more work to maintain as you need 2 sets of install media etc. etc.
-
29 Mei 2012 14:21
Ok thanks for the insight. I managed to get my computer naming working correctly using both MAC and serial so i felt some amount of progression.... then i hit another stumbling block, going back to naming computers.... i dont know how big your environment is, but we do not have system center products at all to help us, it is purely MDT. let's say for example i have 50 computers to deploy, some are laptops and others are desktops, we use two different manufacturers and of course being the good IT pro i am, i have all the serial numbers logged on my asset inventory for every machine.
having said that, how on earth do you go about naming 50 machines, you cant use the make/model because that would mean all machines with that make/model will recieve the same name which you cant have... but to create 50 records based on serial (or MAC, whichever) just to assign a computer name.... there's no copy and paste function to copy the initial record you set up then just edit the serials and names...
so how do you go about naming computers when you have a large batch of them to do?
many thanks
Steve
-
30 Mei 2012 12:36
All you do is add each machine into the MDT database and store its serial there and then set the OSDComputerName property to the name you want to assign that computer.
This way anytime you do an install using MDT it will check the serial of the computer you are installing on and then try and lookup that serial in the database to find the correct computer name to assign.
Assuming you can export the serials and computer names of your existing computers from your asset software you should be able to speed up the process of populating the database using this website as a guide: http://pauliddonit.com/?p=228 (using powershell to look through a CSV file containing your computer serials and names and importing them into your MDT database). Once you do this you only have to worry about any new computers you purchase.
-
30 Mei 2012 13:19
Found using SQL management studio handy for populating the database - cut and paste from excel.
http://www.mssqltips.com/sqlservertip/1430/import-excel-data-into-sql-server-using-copy-and-paste/
-
31 Mei 2012 9:41
Ok thank you, not looking as much of a nightmare now, ive created a location record for some other stuff, things are automating nicely now.
on a side note, did you deploy Office 2007/2010 using MDT? if so, did you get outlook to be setup completley automated - no user prompts at all when outlook loads. i posted this question in full at http://social.technet.microsoft.com/Forums/en-us/outlook/thread/cf4eb300-3ded-4c73-b597-d8b68cee0c09 to understand what i'm trying to get at.
many thanks
.png)
