wbinfo -n "Domain Users"

It will spit out the SID for the Domain Users group. Something like this:

S-1-5-21-((some number))-((some number))-((some number)) Domain Group (2)

Take that number and change the Pam_winbind.so line in /etc/pam.d/common-session to look like this:

session sufficient pam_winbind.so require_membership_of=S-1-5-21-((some number))-((some number))-((some number)

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.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

psexec \\[workstation name] powercfg /query
Field Description          Value
-----------------          -----
Name                       Home/Office Desk
Numerical ID               0
Turn off monitor (AC)      After 20 mins
Turn off monitor (DC)      After 5 mins
Turn off hard disks (AC)   After 60 mins
Turn off hard disks (DC)   After 10 mins
System standby (AC)        Never
System standby (DC)        After 5 mins
System hibernates (AC)     Never
System hibernates (DC)     After 20 mins
Processor Throttle (AC)    Not Supported
Processor Throttle (DC)    Not Supported

that will tell you what the current settings are. After that, you can set the power scheme by doing this:

psexec \\[workstation name] powercfg /setactive "[scheme name]"

It will exit with “error code 0″, but no worries. Just check your work using the query command above after your changes.

1. Download the Program from logitech.com
2. use 7-zip, winRAR, or some other decent compression program to extract the contents of the .exe to a folder on you computer.
3. Open up Device Manager. right-click on the unknown USB device, and select “Update Driver”.
4. Point it at the folders you extracted. it should be under a folder appropriately named “drivers”. mine was in “pro”.
5. happy happy. you web cam works without the extra bloat.

runas /user:DOMAIN\ADMIN_ACCOUNT "cmd /c \"c:\program files\microsoft\exchange server\bin\exchange management console.msc\""

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