Jump to content

ghorn

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    SIlver Spring, MD
  • Agent Count
    10000+

Converted

  • OCCUPATION
    Product Engineer
  1. So make a password parameter, and use @password@ Think of parameters as external input you want to pass along. So you could have msiexec /I @pathtomsi@ /qn with pathtomsi as a parameter. I use them for a few things.
  2. In the script editor, click on "Globals and Parameters." On the right, you can add a parameter. The script will prompt you to enter a value for the parameter when it is run, and the variable in the script is represented as @ParameterName@ So in your case, a parameter could be UserName and then you'd have "if @users@ contains @UserName@, jump to X line"
  3. ghorn

    SQLyog

    When I was managing LabTech for three MSPs, I got tired of having to log into different LabTech servers to use SQLyog, so I set up a redirector. It's also helpful for days you may be off site and need to get into SQLyog: Name: SQLyog Program: C:\Program Files\SQLyog Community\SQLyogCommunity.exe Redirector Type: Computer LocalPort: 3306 LocalIP: 127.0.0.1 RemotePort: 3306 RemoteIP: %remoteip% SocketType: 0 SocketFunction: TCPLocalList UPDATE: If you run an instance of SQL on your computer, you need to change "LocalPort" to something other than 3306 (I use 3307), but leave the "RemotePort" as 3306. in SQLyog, when you make your connection, be sure the port you enter is the one you've set as "LocalPort"
  4. Since Microsoft no longer issues service packs as of Windows 8/Server 2012, we would get a lot of false positive service pack missing tickets for newer machines and servers. We resolved the issue by copying the default 'Updates - Missing Service Pack' monitor and making the following changes: Result field: ('5.1.2600 Service Pack 3','5.0.2195 Service Pack 4','6.0.6002 Service Pack 2','5.2.3790 Service Pack 2','6.1.7601 Service Pack 1','6.2.9200','6.3.9600') Additional Condition field: computers.version <> '' and instr(computers.version,',') <1 and instr(computers.os,'CE') <1 and instr(computers.os,'mobile') <1 and instr(computers.os,'linux')<1 and instr(computers.os,'mac os x')<1 and instr(computers.os,'windows 8') <1 and instr(computers.os,'windows 8.1') <1 and instr(computers.os,'windows 10') <1 and instr(computers.os,'windows server 2012 R2') <1 and instr(computers.os,'windows server 2012') <1 and computers.name<>'LabPE'
  5. We filter these to an informational board in CW, where they're auto-closed by a workflow rule. It's an issue of 'we really can't do anything about it, but it's good historical information.' If we have a machine that's acting up, and we can't figure out why, we at least have historical data in the event that there have been problems with heat or voltage spikes.
  6. ghorn

    Get Windows 10 - Make it go away!

    We blacklisted the update.
  7. ghorn

    PowerShell Plugin for LabTech

    May I ask a quick question? One of my peers decided to upgrade PowerShell on his computer from 2.0 to 3.0, and now the plugin doesn't work on his PC. It gives an error: 'powershell is not recognized as an internal or external command, operable program or batch file.
×