Davit2005 Posted June 28, 2013 Posted June 28, 2013 (edited) Were using MDT 2012 to build the Images. We would like to provide the name of the WIM file in something like BGInfo. We can call information such as Build/Deployed date which are currently written to a registry key for this purpose. It really need to be automated so there is no room for human error Even if it is in another key in the registry that would work too. Edited June 28, 2013 by Davit2005
ChrisH Posted June 28, 2013 Posted June 28, 2013 (edited) Like you say I would just add a key for reference somewhere like HKLM\system\setup. Edit Having re-read your post I think it would be useful for you to dump all the task sequence variables to see what is what, I have used something similar when trouble shooting before. http://blogs.technet.com/b/mniehaus/archive/2010/04/26/dumping-task-sequence-variables.aspx Edited June 28, 2013 by ChrisH 1
Davit2005 Posted June 28, 2013 Author Posted June 28, 2013 Yeah we have various Keys produced when image deployed to end machine such as a Date/Time which is handy but would be good if we could write the WIM image name also to a reg key. I looked through the resistry of a built machine but could'nt find any WIM files.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now