Quick nslookup Guide

Posted on January 25, 2011 by Thomas Maurer

This is a quick note how to use nslookup.exe.

Start nslookup and check for domain

C:> nslookup
Default Server:  ns1.corp.pepsi.local
Addresse:  10.10.20.1
> thomasmaurer.ch
Default Server: ns1.corp.pepsi.local
Addresse: 10.10.20.1

Name:    thomasmaurer.ch
Address:  217.26.52.30
>

Change Nameserver for search querys

> server ns2.corp.pepsi.local
Default Server: ns2.corp.pepsi.local
Addresse: 10.10.20.2
>

Set a query type (ex. A,AAAA,A+AAAA,ANY,CNAME,MX,NS,PTR,SOA,SRV)

> set type=mx
> thomasmaurer.ch
Server: ns2.corp.pepsi.local
Address:  10.10.20.2

thomasmaurer.ch MX preference = 10, mail exchanger = mx2.mail.genotec.ch
thomasmaurer.ch MX preference = 10, mail exchanger = mx1.mail.genotec.ch
mx1.mail.genotec.ch   internet address = 217.26.49.141
mx1.mail.genotec.ch   internet address = 217.26.49.140
mx2.mail.genotec.ch   internet address = 217.26.49.139
mx1.mail.genotec.ch   internet address = 217.26.49.142
>

nslookup.exe help

Commands:   (identifiers are shown in uppercase, [] means optional)
NAME            - print info about the host/domain NAME using default server
NAME1 NAME2     - as above, but use NAME2 as server
help or ?       - print info on common commands
set OPTION      - set an option
    all                 - print options, current server and host
    [no]debug           - print debugging information
    [no]d2              - print exhaustive debugging information
    [no]defname         - append domain name to each query
    [no]recurse         - ask for recursive answer to query
    [no]search          - use domain search list
    [no]vc              - always use a virtual circuit
    domain=NAME         - set default domain name to NAME
    srchlist=N1[/N2/.../N6] - set domain to N1 and search list to N1,N2, etc.
    root=NAME           - set root server to NAME
    retry=X             - set number of retries to X
    timeout=X           - set initial time-out interval to X seconds
    type=X              - set query type (ex. A,AAAA,A+AAAA,ANY,CNAME,MX,NS,PTR,SOA,SRV)
    querytype=X         - same as type
    class=X             - set query class (ex. IN (Internet), ANY)
    [no]msxfr           - use MS fast zone transfer
    ixfrver=X           - current version to use in IXFR transfer request
server NAME     - set default server to NAME, using current default server
lserver NAME    - set default server to NAME, using initial server
root            - set current default server to the root
ls [opt] DOMAIN [> FILE] - list addresses in DOMAIN (optional: output to FILE)
    -a          -  list canonical names and aliases
    -d          -  list all records
    -t TYPE     -  list records of the given RFC record type (ex. A,CNAME,MX,NS,PTR etc.)
view FILE           - sort an 'ls' output file and view it with pg
exit            - exit the program

Add Drivers to Windows Installation ISO

Posted on January 24, 2011 by Thomas Maurer

If you have a Windows 7 or even a Windows Server 2008 R2 Server ISO file and you need to add drivers to this ISO file, this little how to shows you how you can do that.

First create the following folders
C:\temp\WindowsISO (Unpack the windows.iso to this folder)
C:\temp\drivers (Add all driver folders in this folder the drivers have to be in .inf format)
C:\temp\wim (Is a temp folder for the WIM file)
C:\ temp\WindowsISOdrivers (the new .ISO file will be created here)
Download and install the Windows Automated Installation Kit
Start Windows AIK Deployment Tools Command Prompt from Start menu

Mount the install.wim file from C:\temp\WindowsISO to C:\temp\wim

imagex /mountrw C:\temp\WindowsISO\SOURCES\install.wim 1 C:\temp\wim

Add Drivers with dism

 CD C:\temp\drivers\Network\Emulex\M72KR\W2K8R2\x64
dism /image:C:\temp\wim /add-driver /driver:. /recurse

Now unmount the WIM Image
```
imagex /unmount /commit C:\temp\wim
```

Create the new ISO file

oscdimg -n -m -bc:\temp\WindowsISO\boot\etfsboot.com C:\temp\WindowsISO C:\temp\WindowsISOdrivers\windows.iso

Error: Unable to get the private bytes memory limit for the W3WP process

Posted on January 19, 2011 by Thomas Maurer

Error

==================
Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1093
Date: 13.01.2011
Time: 11:11:50
User: N/A
Computer: Server01

Description:

Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error: 0×80070005

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==================

Environment

Windows Server 2003
IIS 6
.NET 2.0 and 1.1

Summary

This Error is caused by the a know issue with permissions of the IIS metabase. The metabse ACL’s do not include the IIS_WPG group on the W3SVC/AppPools part in the metabase.

Solution

Download metaacl.vbs
Run the following command:
cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE

More Information

Run Remote Powershell Commands on multiple standalone Computers

Posted on January 18, 2011 by Thomas Maurer

Powershell Header

With this little Powershell Script you can run Powershell Commands on multiple Remotehosts even if those are not in an Active Directory.

# Config
$Servers = @("Server01", Server02)
$Cred = Get-Credential # Add Credentials for all Servers (Domain or non-Domain)

# Run Command (for example Get-Service | Where-Object {$_.Name -eq "BITS"}
foreach ($Server in $Servers) {
	Invoke-Command -ComputerName $Server -Credential $Cred {Get-Service | Where-Object {$_.Name -eq "BITS"}}
}

Important:

You have to enable Powershell Remoting on the Remotehost with Enable-PSRemoting

Quick Powershell Remoting Guide

Posted on January 17, 2011 by Thomas Maurer

Powershell Header This is small guide which allows you to create Remote Powershell Sessions (like SSH). It allows you to create connection to Host which have Powershell Version 2.

Allow Powershell Remoting on the Remotehost
Add Trusted Hosts on the Localcomputer
Create a new Remotesession
Leave a Powershell Remotesession
Close a Powershell Remotesession
Send a command to a Remotehost

Allow Powershell Remoting on the Remotehost

Run Powershell 2.0 on the Remotehost and run the following Cmdlet.

Enable-PSRemoting

This command starts the WinRM service if it’s not allready started and sets the startup type to automatic. Adds firewall exceptions for WS-Management communications and creates a listener to accept requests.

Add Trusted Hosts on the Localcomputer

On the Local Computer run Powershell and run the following Cmdlet. This allows you to connect to any host. It also starts WinRM if its not already started.

Set-Item WSMan:\localhost\Client\TrustedHosts *

After that you may have to restart the WinRM service

Restart-Service winrm -Force

Create a new Powershell Remotesession

There are two ways to create a new PS Remotesession.

New-PSSession -ComputerName Server01

With Get-PSSession you can list all active sessions. Now you can enter a active Session with Enter-PSSession and the ID

Enter-PSSession 2

A quicker way to do that, you can simply use Enter-PSSession to create a new Session and directly connect to this Session.

Enter-PSSession -ComputerName Server02

Leave a Powershell Remotesession

To leave a Powershell Remotesession you can simply use the Exit-PSSession

Exit-PSSession

Close a Powershell Remotesession

To close a Powershell Remotesession you can list all active Sessions with Get-PSSessions and close them with Remove-PSSession.

Get-PSSession | Remove-PSSession

Send a command to a Remotehost

To run a command on a Remotehost you can use the -ComputerName parameter.

Get-Service -ComputerName Server02

Get-Service -ComputerName Server02 | Where-Object {$_.Name -eq "BITS"}

With this little snippet you can run commands on multiple Hosts


$Servers = @("Server01", "Server02")

foreach ($Server in $Servers) {

Write-Host "Server: " $server

Get-Service -ComputerName $server | Where-Object {$_.Name -eq "BITS"}

}

Genotec Hosted SharePoint 2010: SharePoint prompts for login credentials

Posted on January 11, 2011 by Thomas Maurer

If you use a Hosted SharePoint 2010 and you try to open a Word Document or try to open a Document Library with Explorer SharePoint prompts for login credentials even you are already logged in. To stop this behavior in Internet Explorer you can simply add your SharePoint Site to the Local Intranet Zone.

This is because SharePoint uses Windows Authentication. We deiced to use Windows Authentication because only Windows Authentication allows you to easily use the full feature set of SharePoint Foundation 2010.

Open Internet options and click on the Security tab and choose Local Intranet
Now click on Sites. On the first Windows choose Advanced
Now add your SharePoint Site URL
Restart Internet Explorer

SharePoint 2010 Workflow states are grayed out

Posted on January 10, 2011 by Thomas Maurer

When you try to create a three-state workflow in SharePoint 2010 and SharePoint Foundation 2010, the state fields are maybe grayed out like in this screenshot below.

The reason for this is that there is no column to show the states for the documents of the document library. You can simply solve this issue, by adding the “choice” column to the document library.

Choose the document library in which you wanna create the workflow and click on the Library button in the Ribbon
Click on create Column
Choose the type “Choice” and make sure you add three states
Now these states are available in the three-state workflow.