To use pyinstaller:

1. grab pyinstaller 1.5rc (1.4 doesn’t work with python 2.7). extract the zip file anywhere.
2. change directories to the pyinstaller folder you just created.
3. Before you create your first executable, you will have to run this once.

python configure.py

4. Now, pyinstall needs to scan through your program and create what they call a spec file.

python makespec.py --onefile path\to\program\program.py

5. Now, run this command to generate the executable.

python build.py program\program.spec

Once the command has finished, the standalone executable will be available in the program\dist folder inside of pyinstaller.
Instructions for how to do this for a linux executable on ubuntu linux can be found here: http://excid3.com/blog/2009/12/pyinstaller-a-simple-tutorial/. You can find more info on pyinstaller at their website: http://www.pyinstaller.org/.

Windows:
This server seemed to want the license file specified. You may need to launch the lmtools GUI tool and watch the status bar for the path to it. This is what mine looked like:

"c:\program files\autodesk network license manager\lmutil" lmstat -c "c:\program files\autodesk network license manager\license\license.lic" -a

Linux:

/home/esri/arcgis/license10.0/bin/lmutil lmstat -a

That will spit out the current license usage for all your products. To isolate the numbers we want to monitor, we will be piping the output into some other commands like find and cut.
I recommend using the GNU tools for windows http://gnuwin32.sourceforge.net/. These examples use the built-in ‘find’ utility, and a ‘cut.exe’ tool i found googling around. I had overlooked the gnutools when I first set this up. My mistake can be your gain. With gnutools, it will be easy to isolate the output you want using ‘grep’ and ‘cut’. First, isolate the line you are looking for with grep. You will have to figure out what feature code you want to monitor. mine looks like this:

Windows:

"c:\program files\autodesk network license manager\lmutil" lmstat -c "c:\program files\autodesk network license manager\license\license.lic" -a | find /i "64300acd_f:"

Linux:

/home/esri/arcgis/license10.0/bin/lmutil lmstat -a | grep ARC/INFO

now that you have the right line,  you can trim the extra characters with ‘cut’. It will take some experimentation to get it right.:

Windows:

"c:\program files\autodesk network license manager\lmutil" lmstat -c "c:\program files\autodesk network license manager\license\license.lic" -a | find /i "64300acd_f:" | cut -c 62-64

Linux:

/home/esri/arcgis/license10.0/bin/lmutil lmstat -a | grep ARC/INFO | cut -c 59-61

The output now should be only the number of licenses being used.

To allow zabbix to monitor this value, we need to create a ‘UserParameter’ read up on it here: http://www.zabbix.com/documentation/1.8/manual/config/user_parameters. This is what the parameter looks like on my servers:

Windows:

UserParameter=licenses.autocad.used,"c:\program files\autodesk network license manager\lmutil" lmstat -c "c:\program files\autodesk network license manager\license\license.lic" -a | find /i "64300acd_f:" | cut -c 62-64

Linux:

UserParameter=licenses.arcinfo.used,/home/esri/arcgis/license10.0/bin/lmutil lmstat -a | grep ARC/INFO | cut -c 59-61

Once you have the userparameter created on the license server, restart the agent and add an item in zabbix to begin collecting values.

The issue was apparently that if I log into my workstation as a non-administrative user, but try to issue pstools commands as an administrator,  it fails because Microsoft wants me to log into my workstation and work logged with my domain admin account.

Take a look at this example using psexec:
On windows 7, running ‘cmd’ as your non-admin user, if you type in the command:

c:\Program Files (x86)\PsTools>psexec -u domain\domainadmin \\targetmachine cmd

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

Password:
Could not start PsExec service on targetmachine:
Access is denied.

If you:

1. Hit start
2. Type “cmd”
3. Hold down ‘shift’ and right-click on the ‘cmd’ in the start menu
4. Select ‘run as different user’.
5. Type in your administrative credentials. Use the same ones you will use in the psexec command.

Now you should have your command line window open. If you run the same command as earlier:

c:\Program Files (x86)\PsTools>psexec -u domain\domainadmin \\targetmachine cmd

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

Password:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>

Now you’re in!

In Batch files, you can easily check for architecture by using the “processor_architecture” variable. x86 versions of windows will have this set to “x86″, and x64 versions “x64″. Heres an easy example:

@echo off
IF %processor_architecture% == AMD64 echo This is a 64-bit version of windows
IF %processor_architecture% == x86 echo this is a 32-bit version of windows.
pause

@echo off
REM
REM
REM    Detects winzip and silently uninstalls
REM    There is a un-stoppable pop-up window. so this will kill
REM    all instances of  IE after the UN-installation.
REM
REM
REM
taskkill /F /IM wzqkpick.exe
wmic product where "name like '%%winzip%%'" call Uninstall
REM
REM This section is for WinZip <12
REM
If Exist "%programfiles(x86)%\Winzip\winzip32.exe" GOTO 64
If Exist "%programfiles%\Winzip\winzip32.exe" "%programfiles%\WinZip\Winzip32.exe" /Uninstallx
taskkill /F /IM iexplore.exe
GOTO :END
:64
"%programfiles(x86)%\WinZip\Winzip32.exe" /Uninstallx
taskkill /F /IM iexplore.exe
:END

For getting rid of WinZip 12, the magic happens in the 'wmic' line. It searches all of the installed product's names for "winzip" and will uninstall anything it finds. This only works for products that use MSI's. If you ran this outside of a batch file, you will have to use a single % percentage sign instead of the %% double percentage sign... Windows scripting sucks, and that's just the way it is. Same thing that happens in "FOR" loops.

I never knew anything about the Windows management instrumentation control (wmic) until now, but I will be sure to exploit it's features.

pscp -r -P 22 jimmy@johnscomputer.com:/home/jimmy/stuff "c:\documents and settings\jimmy\Desktop"

The “-r” makes it grab the whole folder, and everything under. the “-P” specifies a port (mostly useful if you aren’t using 22. make sure it is capital).

1. Open the Exchange Management Console.
2. Expand Recipient Configuration.
3. Click on Mailbox.
4. In the Mailbox pane, click on New Mailbox…
5. For our purposes, we will pick “room mailbox” This is a mailbox to be assigned specifically to Meeting Rooms. Its associated user account will be disabled in Active Directory.
6. In the User Type window, we can choose either to create a new user or to assign an existent user to the new resource mailbox. If we choose to assign it to an existent user, we will have to check if the account does not already have a mailbox associated to it. Click Next to continue.
7. In the User Information window, we should fill out the user’s personal information and select the Organization Unit where it will be created. After that click on Next
8. On the Mailbox Settings page, we can define the mailbox information such as Alias, Mailbox Server, and Mailbox Store where the new resource mailbox will be located. The policies for Mailbox and ActiveSync can also be defined in this step. We can choose which fields we are going to fill out and then click Next to continue.
9. In the New Mailbox window, we will get a summary of all the information that we have selected in the previous steps. These parameters will be used by the cmdlet New-Mailbox for the creation of this resource mailbox object. To create the resource mailbox, click on New.
10. In the Completion window, we will see the cmdlet New-mailbox and the parameters that we used in the creation process of this new resource mailbox.
11. Grant yourself and users who will manage the mailbox “full access”. Right-click on the mailbox you just created and select manage full access permission.
12. Sign into OWA.
13. Click the dropdown next to your username on the upper-right corner of the screen and open up the room mailbox you just created.
14. go to Options, then Resource settings
15. go through these.
16. Add the room mailbox to outlook.
17. go to the calendar, right-click on the room’s calendar, go to properties.
18. Under the permissions tab, set the default permission to “reviewer”. This will let everyone see what is going on in the room when they are scheduling

props to: http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/managing-resource-mailboxes-exchange-server-2007-part1.html

apt-get install samba

edit the config:

nano /etc/samba/smb.conf

set security to “share”

security = share

and guest account to nobody

guest account = nobody

then you just need to create your share like this:

[guest share]
comment = a guest share
path = /path/to/files
browseable = yes
read only = yes
guest ok = yes