Token Woes
Submitted by kpjernigan on 5 June, 2008 - 12:41.
Here's my dilema.
I have a script that is triggered after an image has been deployed and Windows has finished its mini-setup that runs and creates a registry key on the target PC.
The key includes the DATE and TIME the image was created and supposedly the user that is logged into the DS.
Well %DATE% & %TIME% work fine. %JOBUSER% is blank. If I run that job manually w/o scheduling it puts in the name. But when it's sceduled from a "Success" conditon on the Image Job, nothing shows up for %JOBUSER%.
------------------------------------------------
[HKEY_LOCAL_MACHINE\SOFTWARE\Corporate Image]
"Image Deployment Date"="%DATE%"
"Image Deployment Time"="%TIME%"
"Image Deployment Tech"="%JOBUSER%"
------------------------------------------------
Is there a custom SQL query token that could be written instead... a reference of a different table by using a SQL Query? ... something... I'm grasp'n at straws here. :)
Any suggestions?
We'd like to be able to get the tech that imaged the machine coded into the registry so we can have the NS report on who imaged what, and with what version of our image.
(2 votes)
- Login or register to post comments
- 227 reads
- Printer-friendly version
I think you need security running to do this
I have seen comments similar to this that were talking about doing e-mail jobs and having the same problem with that token.
The resolution seems to be to have security enabled on the console. I know when I set it up on mine, I had no issues with the e-mail part and the %JOBUSER% was the person logged into the DS.
Give that a try and see if it helps.
Yea we already have
Yea we already have security enabled. That's why it works if you manually run that job. But if it's triggered off of another job condition, it leaves it blank.