<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>!NSFW &#187; windows</title>
	<atom:link href="http://nsfw.ibnmasud.com/category/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://nsfw.ibnmasud.com</link>
	<description>Safe for Work</description>
	<lastBuildDate>Thu, 13 Oct 2011 16:48:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Remote management of Exchange 2010 using PowerShell</title>
		<link>http://nsfw.ibnmasud.com/remote-management-of-exchange-2010-using-powershell/</link>
		<comments>http://nsfw.ibnmasud.com/remote-management-of-exchange-2010-using-powershell/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 16:57:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=118</guid>
		<description><![CDATA[You can run powershell commands on your Exchange 2010 server from machines whether or not they have the Exchange Management Tools installed using implicit remoting. Even when you run the Exchange Management Shell on your exchange server, you&#8217;re essentially creating a powershell remoting session. The following steps take place in the background when you click [...]]]></description>
			<content:encoded><![CDATA[<p>You can run powershell commands on your Exchange 2010 server from machines whether or not they have the Exchange Management Tools installed using implicit remoting.</p>
<p>Even when you run the Exchange Management Shell on your exchange server, you&#8217;re essentially creating a powershell remoting session. The following steps take place in the background when you click the EMS icon:</p>
<li>Load the Microsoft.Exchange.Management.PowerShell.E2010 snap-in gets loaded</li>
<li>The RemoteExchange.ps1 script is dot sourced</li>
<li>The Connect-ExchangeServer function is executed</li>
<p>You can set up implicit remoting from any maching using powershell v2. This imports the commands from your exchange server to your local powershell session so you don&#8217;t need any Exchange tools installed.</p>
<p>First we create a session using the New-PSSession cmdlet:</p>
<p><code>$s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://&lt;CAS FQDN&gt;/PowerShell/ -Authentication Kerberos</code></p>
<p>Then, import the session using the Import-PSSession cmdlet:</p>
<p><code>Import-PSSession $s</code></p>
<p>The Exchange Management Shell commands are now imported into the local PowerShell session.</p>
<p>You could use the same method to setup a scheduled task from your machine to run a commands on your exchange server.</p>
<p>[source: <a href="http://www.mikepfeiffer.net/2010/02/managing-exchange-2010-with-remote-powershell/"> ]</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/remote-management-of-exchange-2010-using-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Batch editing Dial-up or VPN access settings in Active Directory</title>
		<link>http://nsfw.ibnmasud.com/batch-editing-dial-up-or-vpn-access-settings-in-active-directory/</link>
		<comments>http://nsfw.ibnmasud.com/batch-editing-dial-up-or-vpn-access-settings-in-active-directory/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 17:00:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[2003]]></category>
		<category><![CDATA[active directory]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=88</guid>
		<description><![CDATA[Script to edit Remote Access Permissions in the Dial-in tab in Active Directory for multiple users in an OU.]]></description>
			<content:encoded><![CDATA[<p>Active Directory doesn&#8217;t let you edit the Dial-up of VPN access policies for multiple users at once through the GUI. You have to edit this setting one at a time for each user. This can be painstaking if you a lot of users. Luckily there is a VB script available like for almost everything else in AD.<br />
<code><br />
Dim aConnection, aCommand, aResult, strLDAPPath, user, objUser<br />
Const ADS_PROPERTY_CLEAR = 1<br />
strLDAPPath = InputBox("Please enter the LDAP path of the OU:")<br />
WScript.Echo strLDAPPath<br />
Set aConnection = CreateObject("ADODB.Connection")<br />
Set aCommand = CreateObject("ADODB.Command")<br />
aConnection.Provider = "ADsDSOObject"<br />
aConnection.Open<br />
aCommand.ActiveConnection = aConnection<br />
aCommand.CommandText="<LDAP://" &#038; strLDAPPath &#038; ">;(&#038;(objectCategory=Person)(objectClass=User));distinguishedName;subTree"<br />
Set aResult = aCommand.Execute()<br />
Do While Not aResult.EOF<br />
	strDN = aResult.Fields("distinguishedName")<br />
	WScript.Echo strDN<br />
	Set objUser = GetObject("LDAP://" &#038; strDN)<br />
'	Comment the following line to manage connection through Remote Access Policy<br />
	objUser.Put "msNPAllowDialin", FALSE<br />
'	Uncomment the following line to manage connection through Remote Access Policy<br />
'	objUser.PutEx ADS_PROPERTY_CLEAR, "msNPAllowDialin", 0<br />
	objUser.SetInfo<br />
	aResult.MoveNext<br />
Loop</p>
<p></code><br />
This script will update the access settings for a group of users in a particular OU. Once you run the script, a dialog box will ask you for this OU. Once this is set all users in that OU will be updated. </p>
<p>The AD property this script modifies is &#8216;msNPAllowDialin&#8217;. This property is accepts boolean values. So the three options are </p>
<li>TRUE (to allow access)</li>
<li>FALSE (to deny access)</li>
<p>To manage access via the Remote Access Policy, comment out the<br />
<code><br />
	objUser.Put "msNPAllowDialin", FALSE<br />
</code><br />
and uncomment the<br />
<code><br />
'	objUser.PutEx ADS_PROPERTY_CLEAR, "msNPAllowDialin", 0<br />
</code><br />
line.</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/batch-editing-dial-up-or-vpn-access-settings-in-active-directory/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to tell if .Net Framework is installed</title>
		<link>http://nsfw.ibnmasud.com/how-to-tell-if-net-framework-is-installed/</link>
		<comments>http://nsfw.ibnmasud.com/how-to-tell-if-net-framework-is-installed/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 17:59:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=72</guid>
		<description><![CDATA[The officially supported method of detecting the presence of the .NET Framework 2.0 is to check the following registry key/value: [HKEY_LOCAL_MACHINE\Software\Microsoft\Net Framework Setup\NDP\v2.0.50727] Install = 1 (REG_DWORD)]]></description>
			<content:encoded><![CDATA[<p>The officially supported method of detecting the presence of the .NET Framework 2.0 is to check the following registry key/value:</p>
<p><code>[HKEY_LOCAL_MACHINE\Software\Microsoft\Net Framework Setup\NDP\v2.0.50727]<br />
Install = 1 (REG_DWORD)</code></p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/how-to-tell-if-net-framework-is-installed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change password from the command line</title>
		<link>http://nsfw.ibnmasud.com/change-password-from-the-command-line/</link>
		<comments>http://nsfw.ibnmasud.com/change-password-from-the-command-line/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 15:50:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[howto password windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/change-password-from-the-command-line/</guid>
		<description><![CDATA[net user &#60;username&#62; &#60;password&#62; Or if you want to hide the password and enter it at a prompt net user &#60;username&#62; *]]></description>
			<content:encoded><![CDATA[<p><code>net user &lt;username&gt; &lt;password&gt;</code><br />
Or if you want to hide the password and enter it at a prompt<br />
<code>net user &lt;username&gt; *</code></p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/change-password-from-the-command-line/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Allowing non-admin Windows users to change IP addresses</title>
		<link>http://nsfw.ibnmasud.com/allowing-non-admin-windows-users-to-change-ip-addresses/</link>
		<comments>http://nsfw.ibnmasud.com/allowing-non-admin-windows-users-to-change-ip-addresses/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 15:34:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[2003]]></category>
		<category><![CDATA[vista]]></category>
		<category><![CDATA[xp]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=54</guid>
		<description><![CDATA[How to allow non-admin users change their IP address.]]></description>
			<content:encoded><![CDATA[<p>If you want to allow non-admin users in Windows to change the IP address settings on their PCs, you can add them to the built-in &#8220;Network Configuration Operators&#8221; group. This can be done from the command line as</p>
<p><code>net localgroup "Network Configuration Operators" /add &lt;username&gt;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/allowing-non-admin-windows-users-to-change-ip-addresses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Install Office 2003 without a CD key ..sort of</title>
		<link>http://nsfw.ibnmasud.com/install-office-2003-without-a-cd-key-sort-of/</link>
		<comments>http://nsfw.ibnmasud.com/install-office-2003-without-a-cd-key-sort-of/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 20:21:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=49</guid>
		<description><![CDATA[Office 2003 wont install unless you supply a valid license key, unlike Office 2007 which lets you enter the key once you&#8217;re done installing. This is very inconvenient when you&#8217;re trying to create a base image of a system to deploy on multiple PCs. You can&#8217;t have the same Office license key for all the [...]]]></description>
			<content:encoded><![CDATA[<p>Office 2003 wont install unless you supply a valid license key, unlike Office 2007 which lets you enter the key once you&#8217;re done installing. This is very inconvenient when you&#8217;re trying to create a base image of a system to deploy on multiple PCs. You can&#8217;t have the same Office license key for all the PCs.</p>
<p>In order to get somewhat similar functionality as Office 2007, i.e., install without key to be filled in later, use the following method. You will still need a valid serial key for the first install, but it will be cleared after its completed.</p>
<p><code>setup.exe /QB PIDKEY=YOURSERIALHERE<br />
regedit /S  clear-key.reg</code></p>
<p>The first line installs office silently with the specified key, and second line clears the registration information. The clear-key.reg file contains the following registry key</p>
<p><code>Windows Registry Editor Version 5.00<br />
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Registration]<br />
</code></p>
<p>Now when you run Office, it&#8217;ll ask you for a license key.</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/install-office-2003-without-a-cd-key-sort-of/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Allowing non-admins to manage services in Windows</title>
		<link>http://nsfw.ibnmasud.com/allowing-non-admins-to-manage-services-in-windows/</link>
		<comments>http://nsfw.ibnmasud.com/allowing-non-admins-to-manage-services-in-windows/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 14:39:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=44</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>This <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;288129">Microsoft KB article</a> lists 3 ways to grant non-admin users the rights to manage services on a windows machine.</p>
<p>Method 1: Grant rights using Group Policy<br />
Method 2: Grant rights using Security templates<br />
Method 3: Grant rights using Subinacl.exe</p>
<p>The easiest and fastest method? Method 3 using subinacl.<br />
<code>SUBINACL /SERVICE \\MachineName\ServiceName /GRANT=[DomainName\]UserName[=Access]</code></p>
<p>[Source: <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;288129">How to grant users rights to manage services in Windows 2000</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/allowing-non-admins-to-manage-services-in-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manage Exchange mailboxes from the command-line</title>
		<link>http://nsfw.ibnmasud.com/manage-exchange-mailboxes-from-the-command-line/</link>
		<comments>http://nsfw.ibnmasud.com/manage-exchange-mailboxes-from-the-command-line/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 22:58:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[cmd]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=36</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p><a title="ExchMbx Download Page" href="http://www.joeware.net/freetools/tools/exchmbx/index.htm">ExchMbx</a> 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.</p>
<p>Ex1:<br />
<code>ExchMbx -b cn=joe,dc=joe,dc=net -cr srv1:sg1:db2</code><br />
Create mailbox for joe in Server srv1, storage group sg1, database db2.</p>
<p>Ex2:<br />
<code>ExchMbx -b cn=joe,dc=joe,dc=net -move srv1:sg1:db2</code><br />
Ditto ex1 but move.</p>
<p>Ex3:<br />
<code>ExchMbx -b cn=joe,cn=users,dc=joe,dc=net -clear</code><br />
Clear Exchange attrs for joe, will delete mailbox or<br />
clean email addresses of mailenabled objects.</p>
<p>Ex4:<br />
<code>ExchMbx -b cn=gr1,cn=users,dc=joe,dc=net -me</code><br />
Mail Enable group gr1</p>
<p>Ex5:<br />
<code>ExchMbx -b cn=con1,cn=users,dc=joe,dc=net -me joe@joeware.net</code><br />
Mail Enable contact con1 with email address joe@joeware.net</p>
<p>ExchMbx can be obtained from <a title="joeware.net" href="http://www.joeware.net/freetools/index.htm">joeware.net</a> along with many other useful tools.</p>
<p>[examples sourced from the <a title="ExchMbx Usage Page" href="http://www.joeware.net/freetools/tools/exchmbx/usage.htm">ExchMbx Usage page</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/manage-exchange-mailboxes-from-the-command-line/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Configuring TCP/IP from the cmd line in Windows</title>
		<link>http://nsfw.ibnmasud.com/setting-an-ip-address-from-the-cmd-line-in-windows/</link>
		<comments>http://nsfw.ibnmasud.com/setting-an-ip-address-from-the-cmd-line-in-windows/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 15:48:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/setting-an-ip-address-from-the-cmd-line-in-windows/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>Netsh.exe can be very useful in viewing and editing TCP/IP settings from the command line. </p>
<p>To <strong>view your TCP/IP settings</strong> in a Command Prompt, type<br />
<code>netsh interface ip show config</code></p>
<p>To <strong>configure an IP address</strong> and other TCP/IP related settings:<br />
<code>netsh interface ip set address name="Local Area Connection" static 192.168.1.101 255.255.255.0 192.168.1.1 1</code></p>
<p>To <strong>obtain an IP address from a DHCP server</strong>:<br />
<code>netsh interface ip set address "Local Area Connection" dhcp</code></p>
<p>To <strong>configure DNS and WINS addresses</strong>:<br />
<code>netsh interface ip set dns "Local Area Connection" static 192.168.0.200</code></p>
<p>and this for WINS:<br />
<code>netsh interface ip set wins "Local Area Connection" static 192.168.0.200</code></p>
<p>Or, to <strong>dynamically obtain DNS settings</strong>:<br />
<code>netsh interface ip set dns "Local Area Connection" dhcp</code></p>
<p>As a bonus tip, you can <strong>export your IP settings</strong> to a text file using the following command:<br />
<code>netsh -c interface dump &gt; c:IPSettings.txt</code></p>
<p>To <strong>import the settings</strong>, type<br />
<code>netsh -f c:IPSettings.txt<br />
OR<br />
netsh exec c:location2.txt</code></p>
<p>You can use this to quickly switch between different settings.</p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/setting-an-ip-address-from-the-cmd-line-in-windows/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>psexec to install msi on remote pc</title>
		<link>http://nsfw.ibnmasud.com/psexec-to-install-msi-on-remote-pc/</link>
		<comments>http://nsfw.ibnmasud.com/psexec-to-install-msi-on-remote-pc/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 18:17:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nsfw.ibnmasud.com/?p=26</guid>
		<description><![CDATA[psexec \\remotepc -u Domain\User -p Password msiexec /i "pathto.msi switches"]]></description>
			<content:encoded><![CDATA[<p><code>psexec \\remotepc -u Domain\User -p Password msiexec /i "pathto.msi switches"</code></p>
]]></content:encoded>
			<wfw:commentRss>http://nsfw.ibnmasud.com/psexec-to-install-msi-on-remote-pc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

