Noe and I biked Coyote ridge late yesterday. A few pics from the ridge and a video of me cleaning some steps.
How to configure iSCSI datastore access for multiple ESX servers
01
Jul
This how to is based on the steps to create a new Volume on an EQ PS600X SAN and configure iSCSI initiator access to multiple ESX servers.
Step 1: Create a new volume on the SAN using the EQ Group Manager web interface
-
Create a volume of 1999 GB (1.95TB) as VMWare has a datastore size limitation of 2TB. 1.95TB was recommended as the max size by EqualLogic.
-
During the setup wizard choose restrict access by iSCSI initiator name.
-
Log into the first ESX server through VIC and go to configuration > storage adapter. Under details copy the iSCSI name.
-
Go back to the wizard and paste in the iSCSI name. Finish the wizard to create the volume. We’ll add the other iSCSI names later.
Step 2: Scan and add the new datastore
-
Back in the VIC under configuration > storage adapter click rescan in the top right. Under View you will see the path to the volume you just create.
-
Go to configuration > storage click add storage on the top right.
-
Choose type: Disk/Lun
-
Select the new datastore and finish the wizard.
Step 3: Add volume access for the other ESX iSCSI initiators and add the new datastore.
-
In the Group Manager web interface for the SAN go to Volumes
-
Right click on the new volume and choose View iSCSI settings
-
Click add and enter the name for the second ESX iSCSI initiator. Repeat for any additional ESX servers.
-
Repeat Step 2 above to scan for the new volume and add the new datastore to the rest of the ESX servers.
How to Expand your Subnet
30
Jun
The Problem: You’re network is 10.1.1.1/24. Subnet: 255.255.255.0 You have 254 usable addresses and let’s say 100 of them are part of the DHCP pool. That leaves you with 154 assignable address. That’s plenty you say. That’s what you say today… Next year you need to expand the DHCP pool to support more users and your new virtual environment consumes 25 address not counting the VMs is runs. Now we are close to running out of address.
The Solution: Expand your subnet to open up more usable addresses. First you must decide how many more address you will need to maintain scalability within reason and avoid doing this again next year 
Use this chart to help determine the appropriate subnet.
The How: These are the steps I took to create minimal impact to the network and the end users.
1. In AD Sites & Services add the new subnet, let it replicate across domain controllers.
2. Update the subnet from 255.255.255.0 on all static network devices (switches, printers, servers, firewalls etc).
3. Update the DHCP settings to handout the new subnet to dynamically assigned devices.
Configure Firewall for MS SQL 2008 R2/Windows 2008 R2
25
Jun
This is a nice batch file to automatically configure Windows 2008 and Windows 2008 R2 firewall for MS SQL 2008 R2. Thanks to MrMMills1
@echo off
echo. *** OPENING SQL SERVER PORTS IN THE FIREWALL ***
echo. source “http://rperreaux.spaces.live.com/Blog/cns!5D7BD18D324CBEEF!729.entry?wa=wsignin1.0&sa=289774293″
echo.
echo. Note for Named Instances – SQL mirroring – Dynamic Ports and the firewall
echo. see http://msdn.microsoft.com/en-us/library/cc646023(v=SQL.100).aspx#BKMK_programs
echo. You will need to open firewall ports for your mirroring endpoints and possibly dynamic ports
echo.
echo.
echo. Opening SQL Server TCP 1433
netsh advfirewall firewall add rule name=”SQL Server (TCP 1432)” dir=in action=allow protocol=TCP localport=1433 profile=domain
echo.
echo. Opening SQL Admin Connection TCP 1434
netsh advfirewall firewall add rule name=”SQL Admin Connection (TCP 1434)” dir=in action=allow protocol=TCP localport=1434 profile=domain
echo.
echo. Opening SQL Service Broker TCP 4022
netsh advfirewall firewall add rule name=”SQL Service Broker (TCP 4022)” dir=in action=allow protocol=TCP localport=4022 profile=domain
echo.
echo. Port 135
netsh advfirewall firewall add rule name=”SQL Debugger/RPC (TCP 135)” dir=in action=allow protocol=TCP localport=135 profile=domain
echo.
echo. Opening SQL Browser UDP 1434
netsh advfirewall firewall add rule name=”SQL Browser (UDP 1434)” dir=in action=allow protocol=UDP localport=1434 profile=domain
echo.
echo. Opening Analysis Services TCP 2383
netsh advfirewall firewall add rule name=”Analysis Services (TCP 2383)” dir=in action=allow protocol=TCP localport=2383 profile=domain
echo.
echo. Opening SQL Browser TCP 2382
netsh advfirewall firewall add rule name=”SQL Browser (TCP 2382)” dir=in action=allow protocol=TCP localport=2382 profile=domain
echo.
echo. ***Done ***
Enable JavaScript for administrators in Windows 2008 server
24
Jun
It almost seems that the Administrators group in Windows 2008 is more like Power Users and the only true Admin is the local Administrator. If I didn’t want members of the Administrators group to have full Admin privileges I wouldn’t put them there. Any way, back to the task of enabling JavaScript for members of the “Administrators” group.
1. Log in as local Administrator (machinename\administrator)
2. Open Server Manager
3. On the right hand side scroll down to Security Information and look for Configure IE ESC
4. Under Administrator choose off
Now all members of the “Administrators” group will be able to administer IE internet zones.
