This Microsoft KB article lists 3 ways to grant non-admin users the rights to manage services on a windows machine.
Method 1: Grant rights using Group Policy
Method 2: Grant rights using Security templates
Method 3: Grant rights using Subinacl.exe
The easiest and fastest method? Method 3 using subinacl.
SUBINACL /SERVICE \\MachineName\ServiceName /GRANT=[DomainName\]UserName[=Access]
[Source: How to grant users rights to manage services in Windows 2000]
ExchMbx is a command-line utility that lets you create user mailboxes, mail enable an AD object, move mailboxes and delete mailboxes among other tasks that can be done using the GUI.
Ex1:
ExchMbx -b cn=joe,dc=joe,dc=net -cr srv1:sg1:db2
Create mailbox for joe in Server srv1, storage group sg1, database db2.
Ex2:
ExchMbx -b cn=joe,dc=joe,dc=net -move srv1:sg1:db2
Ditto ex1 but move.
Ex3:
ExchMbx -b cn=joe,cn=users,dc=joe,dc=net -clear
Clear Exchange attrs for joe, will delete mailbox or
clean email addresses of mailenabled objects.
Ex4:
ExchMbx -b cn=gr1,cn=users,dc=joe,dc=net -me
Mail Enable group gr1
Ex5:
ExchMbx -b cn=con1,cn=users,dc=joe,dc=net -me joe@joeware.net
Mail Enable contact con1 with email address joe@joeware.net
ExchMbx can be obtained from joeware.net along with many other useful tools.
[examples sourced from the ExchMbx Usage page]
Netsh.exe can be very useful in viewing and editing TCP/IP settings from the command line.
To view your TCP/IP settings in a Command Prompt, type
netsh interface ip show config
To configure an IP address and other TCP/IP related settings:
netsh interface ip set address name="Local Area Connection" static 192.168.1.101 255.255.255.0 192.168.1.1 1
To obtain an IP address from a DHCP server:
netsh interface ip set address "Local Area Connection" dhcp
To configure DNS and WINS addresses:
netsh interface ip set dns "Local Area Connection" static 192.168.0.200
and this for WINS:
netsh interface ip set wins "Local Area Connection" static 192.168.0.200
Or, to dynamically obtain DNS settings:
netsh interface ip set dns "Local Area Connection" dhcp
As a bonus tip, you can export your IP settings to a text file using the following command:
netsh -c interface dump > c:IPSettings.txt
To import the settings, type
netsh -f c:IPSettings.txt
OR
netsh exec c:location2.txt
You can use this to quickly switch between different settings.
psexec \\remotepc -u Domain\User -p Password msiexec /i "pathto.msi switches"
This one had been bothering me for quite some time now. Ever since upgrading from ISA 2004 to ISA 2006, I noticed that the context menu item for editing the per rule HTTP Filter settings was missing from all the web publishing/access rules.
The only way I could edit these settings was the HTTPFilterConfig.vbs script which is included in the ISA SDK. This script lets you import the filter settings to a rule from an XML file or export them to an XML file from a rule for which the filter settings have already been modified. This works quite well but is a hassle every time a rule needs to be modified.
It turns out that the Web Proxy Filter must be enabled for the HTTP protocol. Without this enabled, you loose the HTTP filter configuration menu. If you dont want to enable the Web Proxy filter, as it may not work well with some sites, enable it temporarily, change the HTTP filter setting and then disable it. The HTTP filter settings will still remain active. Problem solved.
