problem moving from test environment to production (MDT 2008)

[James]

mdt 2008 update 1 running on server 2k8

customized the deployment wizard: wizard.hta, deploywiz_definition_enu.xml,
and wizard.css were modified... also new file included that holds most of
the custom wizard code which is referenced from
deploywiz_definition_enu.xml.

ztiutility.vbs was modified: added custom class which writes to a database,
existing logging class uses this class and all log info goes to the log
files and to a database

those are the files that were modified, no microsoft code was changed, only
additions made... all works GREAT in my test environment. I setup a new
server to be the production server and copied over my scripts from the test
server... however on this server the deployment wizard fails to start! no
errors, no nothing, just sits at the wpeinit screen (the other cmd window
that opens minimized is also there). If I copy the original unmodified
scripts from the new installation back into the distribution share the
wizard starts fine.

anyone have any ideas? does MDT somehow track it's scripts relationship to a
particular installation... I did not try editing original files to include
the code additions yet... but I guess thats probably next for me to try.
Versions of MDT are exactly the same between test and production server.

ugh. I spent a LOT of time doing these customizations... I'm really hoping
I'm just missing something silly here...

[unknown]

Did you create a new boot media by updating the deployment point?
(bootstrap.ini is on the boot media)

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
mdt 2008 update 1 running on server 2k8
customized the deployment wizard: wizard.hta, deploywiz_definition_enu.xml,
and wizard.css were modified... also new file included that holds most of
the custom wizard code which is referenced from
deploywiz_definition_enu.xml.
ztiutility.vbs was modified: added custom class which writes to a database,
existing logging class uses this class and all log info goes to the log
files and to a database
those are the files that were modified, no microsoft code was changed, only
additions made... all works GREAT in my test environment. I setup a new
server to be the production server and copied over my scripts from the test
server... however on this server the deployment wizard fails to start! no
errors, no nothing, just sits at the wpeinit screen (the other cmd window
that opens minimized is also there). If I copy the original unmodified
scripts from the new installation back into the distribution share the
wizard starts fine.
anyone have any ideas? does MDT somehow track it's scripts relationship to a
particular installation... I did not try editing original files to include
the code additions yet... but I guess thats probably next for me to try.
Versions of MDT are exactly the same between test and production server.
ugh. I spent a LOT of time doing these customizations... I'm really hoping
I'm just missing something silly here...

[James]

thanks for the reply Johan. I just posted what it turned out to be....
however,

I wanted to thank you directly anyway, for all the responses I have gotten
from you over the last few months. I am working on a pretty big deployment
of MDT 2008 and you have replied to almost all my posts, if not all of them,
and I REALLY appreciate it. I have also checked out your blogs, which have
been helpful.

you to Dave Guenthner, thanks.

I'm on the final leg of my project so I'm sure at least a few more posts are
coming.

Thank you!

Post by unknown
Did you create a new boot media by updating the deployment point?
(bootstrap.ini is on the boot media)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
mdt 2008 update 1 running on server 2k8
customized the deployment wizard: wizard.hta,
deploywiz_definition_enu.xml,
and wizard.css were modified... also new file included that holds most of
the custom wizard code which is referenced from
deploywiz_definition_enu.xml.
ztiutility.vbs was modified: added custom class which writes to a database,
existing logging class uses this class and all log info goes to the log
files and to a database
those are the files that were modified, no microsoft code was changed, only
additions made... all works GREAT in my test environment. I setup a new
server to be the production server and copied over my scripts from the test
server... however on this server the deployment wizard fails to start! no
errors, no nothing, just sits at the wpeinit screen (the other cmd window
that opens minimized is also there). If I copy the original unmodified
scripts from the new installation back into the distribution share the
wizard starts fine.
anyone have any ideas? does MDT somehow track it's scripts relationship to a
particular installation... I did not try editing original files to include
the code additions yet... but I guess thats probably next for me to try.
Versions of MDT are exactly the same between test and production server.
ugh. I spent a LOT of time doing these customizations... I'm really hoping
I'm just missing something silly here...

[James]

I just figured it out... a BIG duh, on my part. The logging system is
writting information even BEFORE you see the wizard appear... my wizard
never appeared because the logging system, which I added a database function
to, could not connect to the database! It was an sql server thing (simply
forgot to enable tcpip for remote connections). What a relief.

I assume there was no error info anywhere because of where the error was
occuring, within the logging class in ztiutility.vbs itself, which makes
calls to my added db class, and the logging class is involved in error
handling since errors are well, logged..? ..?

I fixed database config and all is working again, so far...

Post by James
mdt 2008 update 1 running on server 2k8
customized the deployment wizard: wizard.hta,
deploywiz_definition_enu.xml, and wizard.css were modified... also new
file included that holds most of the custom wizard code which is
referenced from deploywiz_definition_enu.xml.
ztiutility.vbs was modified: added custom class which writes to a
database, existing logging class uses this class and all log info goes to
the log files and to a database
those are the files that were modified, no microsoft code was changed,
only additions made... all works GREAT in my test environment. I setup a
new server to be the production server and copied over my scripts from the
test server... however on this server the deployment wizard fails to
start! no errors, no nothing, just sits at the wpeinit screen (the other
cmd window that opens minimized is also there). If I copy the original
unmodified scripts from the new installation back into the distribution
share the wizard starts fine.
anyone have any ideas? does MDT somehow track it's scripts relationship to
a particular installation... I did not try editing original files to
include the code additions yet... but I guess thats probably next for me
to try. Versions of MDT are exactly the same between test and production
server.
ugh. I spent a LOT of time doing these customizations... I'm really hoping
I'm just missing something silly here...