Jump to content

MSTechNate

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
    1500+
  1. This is working for us too. If you're running the LT client as a RemoteApp (or via Citrix), you must also include the argument --allow-no-sandbox-job - otherwise, Chrome launches, but won't do anything.
  2. I had posted a working vSphere redirector in this forum - check a few threads down.
  3. or, how to get your techs to tell you they love you. Make your VNC settings and LabVNC redirector settings match the screenshots below.
  4. That is awesome. I'm going for my VCP-DV later this month - that will come in handy!
  5. You may want to edit the OP - you forgot to include the location ID argument in the example
  6. I'd suggest hopping in ##labtech (irc.freenode.net) and posing the question there. Perhaps someone else has seen that error before.
  7. http://YOURSERVER/Labtech/Deployment.aspx?Probe=1&MSILocations=1 The 1 at the end is the location ID you want to generate the MSI for. Once I have some free cycles, I'm going to do something very, very cool with this.
  8. This script uses a tweaked Smart Installer filename that doesn't rely on having to set any EDFs in Labtech. Grab your Smart Installer from your ESET server and edit out the last two parts of the filename, leaving the commas in place. It should look something like this when you're done: SmartInstaller,your-eset.fqdn.com,ESET NOD32 Antivirus BUSINESS EDITION,EAVBE,LABTECH,,.exe Copy this file to LTShare\Transfer\ESET. Import the attached script and edit lines 1 and 6, replacing with the real name. When you run the script, it will download the Smart Installer to c:\ESETInstall and fire it off. It checks periodically to see if the Smart Installer component (emu-cci.exe) is still running, and if so, waits a bit more. If ESET isn't running (ekrn.exe) once emu-cci completes, it assumes the install has failed. NOD32 Smart Install - MSTech.zip
  9. With the help of Greg Buerk and mtp_brendan from IRC, I was able to get a working vSphere Client redirector. Caveats: if you're connecting to a vCenter server, you won't be able to view the console of any VMs (MKS) - this is because the vSphere Client makes a direct connection to the ESXi server on port 902. If you connect directly to the ESXi host, MKS works fine. Here's how to set it up: 1.) Create a new redirected app named vSphere Client. 2.) In the program field, enter C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe (or whatever the path is to vpxclient.exe on your system) 3.) You'll need to redirect a handful of ports. These are for ESXi 5.x, and were gleaned from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012382 Local Port: 443 Local IP: 127.0.0.1 Remote Port: 443 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 902 Local IP: 127.0.0.1 Remote Port: 902 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 903 Local IP: 127.0.0.1 Remote Port: 903 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 8080 Local IP: 127.0.0.1 Remote Port: 8080 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 9443 Local IP: 127.0.0.1 Remote Port: 9443 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 10080 Local IP: 127.0.0.1 Remote Port: 10080 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 10443 Local IP: 127.0.0.1 Remote Port: 10443 Remote IP: %RemoteIP% Type: TCP Local Listen Local Port: 902 Local IP: 127.0.0.1 Remote Port: 902 Remote IP: %RemoteIP% Type: UDP Local Listen Note that the last one is UDP. In theory, you really only need 443 and 902, but I couldn't make the connection with just those. 4.) One more step - I had to do this, mtp_brendan did not. Create an entry in your hosts file for "127.0.0.1 vsphere-redir". If you just use 127.0.0.1 or localhost, vSphere may actually try to connect to the NetBIOS name of your PC, which won't work. 5.) Once you've got everything configured, you can connect directly to an ESXi host by holding Shift while clicking on the vSphere Client redirector entry. This will prompt you for an IP - enter the IP of the ESXi host. Regardless of whether you're connecting directly to a host, or to vCenter, you'll always enter vsphere-redir as the host in the vSphere Client itself. Good luck!
  10. This script will find any scripts that have their edit permissions or read/execute permissions set to 0, (which means that EVERYONE can access the script) and update it with permissions for the user classes you specify. You'll need to figure out the user class ID(s) of the classes you want to have and edit the script variables appropriately. These can be found by looking at the userclass table. The script also includes the ability to overwrite permissions on a certain script folder ID every time it runs. This can be useful if you have some scripts that only super admins should have access to. If you don't want to use the admin scripts feature, make sure you disable the appropriate script step (documented in the script itself). Make sure you read through the script an understand what it does. Feel free to ping me in IRC (##labtech) with any questions. Set Default Script Permissions - Shared.zip
×
×
  • Create New...