If you are a LabTecher then this is a must-attend event: Automation Nation 2013 is finally here! I'll be there Tuesday and if you tell me you're a reader of this blog, you'll win a free drink. You can two-fer it if you tell me you've also run one of my posted scripts, either from here or LabTech Geek but be prepared for questions!
Happy LabTeching everyone, hope to see you in Orlando.
Random musings of a LabTech Teacher (Standard Disclaimer: This site is unoffical!!)
Sunday, June 2, 2013
Can LabTech modify a/some/all user profiles?
Of course.
Normally I don't recommend a script I haven't first tested, but as it's from The Man, it's probably a safe bet.
Nonetheless, all standard disclaimers apply. ;)
Normally I don't recommend a script I haven't first tested, but as it's from The Man, it's probably a safe bet.
Nonetheless, all standard disclaimers apply. ;)
Thursday, May 30, 2013
Are you a LabTech Geek?
Then you ought to know about this: http://www.labtechgeek.com
Happy LabTeching!
Happy LabTeching!
Friday, May 3, 2013
Update
I know I've two half-written articles below. Be patient, dear reader! I'll come back to them soon enough but having learned a great deal about PSA's over the last couple weeks has made me rethink the Guns and Butter article. I may have lept to an incorrect assumption and want to dig deeper before making a final judgement on this. Regardless of the result, I must admit it really looks as though I may have made a rash initial decision.
Tuesday, April 30, 2013
Solved: How to enable LabTech remote uninstall
Uninstall Application vs. Uninstall Application User. What's the difference and why are there two buttons for one process? The most common workflow when someone new to LabTech finds the software uninstall option is to try it, then report to support it doesn't work. What is going on under the covers and (more importantly) how do you make it work?
This command is no different from most other LabTech commands in that its run by the Local System Account (LSA). What happens when you press that button is the exact same thing as if you did it on the local computer in Add\Remove Programs. 99 times out of 100, you'll be prompted 'Are you sure?' Thing is, the LSA can not paint to the desktop so no one can ever see that prompt. It sits and waits for a response that never comes and meanwhile it looks to the technician that the command has failed.
If you're skeptical try this next time: send the command to refresh the local processes. I bet you'll see an msiexec.exe in there. That's your uninstall prompt waiting for a response and that's the point of Uninstall Application User - it is run by the LabTech Tray (which is running in the user's security context) so the user will see the prompt and can click it for you. In a pinch that's OK but we don't want to build a service offering around that jenked process. How do we click that button?
We can't - we have to make it so that dialogue never occurs, just like if you had checked the 'In the future, don't show me this dialogue box'. How do we do that progromatically? Simple - use the registry!
You should use this process on every application you deploy thru LabTech. This way, anytime you need to un\re install an app, you won't need to interrupt the user and you'll have 100% full control of all the application on a remote computer. For example, on my ConnectWise install script, I've the following line:
Registry Set Value: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\DontShowMeThisDialogAgain\{948e51fb-0a48-44f0-86ac-33c36def540c} = NO (reg_sz)
Now my right-click, uninstall application button in LabTech works flawlessly.
Remember, real men don't click. (hat-tip to an old web page that was mighty helpful back in the day) Hope this tip helps you in your endeavors and Happy LabTeching everyone!
This command is no different from most other LabTech commands in that its run by the Local System Account (LSA). What happens when you press that button is the exact same thing as if you did it on the local computer in Add\Remove Programs. 99 times out of 100, you'll be prompted 'Are you sure?' Thing is, the LSA can not paint to the desktop so no one can ever see that prompt. It sits and waits for a response that never comes and meanwhile it looks to the technician that the command has failed.
If you're skeptical try this next time: send the command to refresh the local processes. I bet you'll see an msiexec.exe in there. That's your uninstall prompt waiting for a response and that's the point of Uninstall Application User - it is run by the LabTech Tray (which is running in the user's security context) so the user will see the prompt and can click it for you. In a pinch that's OK but we don't want to build a service offering around that jenked process. How do we click that button?
We can't - we have to make it so that dialogue never occurs, just like if you had checked the 'In the future, don't show me this dialogue box'. How do we do that progromatically? Simple - use the registry!
You should use this process on every application you deploy thru LabTech. This way, anytime you need to un\re install an app, you won't need to interrupt the user and you'll have 100% full control of all the application on a remote computer. For example, on my ConnectWise install script, I've the following line:
Registry Set Value: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\DontShowMeThisDialogAgain\{948e51fb-0a48-44f0-86ac-33c36def540c} = NO (reg_sz)
Now my right-click, uninstall application button in LabTech works flawlessly.
Remember, real men don't click. (hat-tip to an old web page that was mighty helpful back in the day) Hope this tip helps you in your endeavors and Happy LabTeching everyone!
Tuesday, April 23, 2013
Does anyone have any experience with Adguard? It seems to work very well with little overhead - can anyone out there say differently?
Tuesday, April 2, 2013
Find the last computer that joined your LabTech Server
Quick and easy:
SET: @sqlIdOutput@ = SQLRESULT[SELECT MAX(ComputerId) FROM computers]
SET: @sqlClientNameOutput@ = SQLRESULT[SELECT clients.name FROM clients JOIN computers USING(clientid) WHERE computerid = '@sqlIdOutput@']
Create Informational Alert on ComputerID #1: The latest computer ID is @sqlIdOutput@ and can be found as a member of the @sqlClientNameOutput@ client.
[UPDATE]
(Hat tip to fellow LabTecher Kevin D for calling this out)
It seems there's an assumption in this logic. It holds - UNLESS you've used the resignup utility. If you have, we can't assume the highest computer ID = the last computer to be added. Thanks Kev! (sorta.. )
SET: @sqlIdOutput@ = SQLRESULT[SELECT MAX(ComputerId) FROM computers]
SET: @sqlClientNameOutput@ = SQLRESULT[SELECT clients.name FROM clients JOIN computers USING(clientid) WHERE computerid = '@sqlIdOutput@']
Create Informational Alert on ComputerID #1: The latest computer ID is @sqlIdOutput@ and can be found as a member of the @sqlClientNameOutput@ client.
[UPDATE]
(Hat tip to fellow LabTecher Kevin D for calling this out)
It seems there's an assumption in this logic. It holds - UNLESS you've used the resignup utility. If you have, we can't assume the highest computer ID = the last computer to be added. Thanks Kev! (sorta.. )
Subscribe to:
Posts (Atom)