Dell ExtPart.exe; Extend Volumes Easily.

This is a great little tool if you wanna extend the OS drive of a VM. Go into vShere and give your VM's OS HD an extra few gigs.

BTW - you can do this HOT. So, if you're going from a 20GB drive to a 40GB drive, then you will run this little exe from the VM itself. Opens a CMD window.

Volume to Extend, type C:
Size to expand the volume, type  20480

now go check your HD size in Windows Explorer :)

Download it here: Dell ExtPart

WordPress on Windows 2008 R2 IIS7.5 - FTP update?

Screw that.

I added the folder permissions of Modify, Read & Execute, List Folders, Read and Write on the c:\inetpub\SiteName folder to ServerName\IUSR

tada... :)

RDP - on a different port than 3389

If you want your server(s) to listen on another port than 3389 for RDP access, then you will need to modify the following registry key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp] Port Number

SQL Server 2008 R2 - 2 node cluster build

SQL 2008 R2 on Windows Server 2008 R2 Clustered install

On both nodes

- need .NET 3.5 SP1 use the Role Management Tool

- Add Role - Application Server

Run the setup.exe - SQL Server Installation Center

- Click Installation on left > New SQL Server Failover installation

- Setup suport Rules - click OK

- Prod Key - click next

- EULA - accept - next

- Click Install

- Setup support Rules - will tell you more about what else you might want to install for this to work.

-  - MSDTC - not always needed for cluster. install if you want.

-  - MSCS - cluster validation report failure - http://support.microsoft.com/kb/953748 - if you havent validated your cluster, you get an error when trying to install - go to Failover Cluster manager and click Validate this cluster.

- prod key - click next

- EULA - accept - next

- Feature Selection - Database Services, Analysis Services, Reporting Services - next

-

Instance Config

- SQLServer Network Name - obxSQL0801

- Named Instance - SQL1

- next

Disk Space Reqs - you will need at least 4 or 5 gbs of local disk space if you're going to install the services I listed above.  I had to go back and shut down my vms and cut a D drive (thin-vhd) of 20GB on each of my nodes. then you can install all your SQL bits on the new D drive instead of on the OS drive.

- instance root directory - d:\

- next

Cluster Resource Group

- SQL Server cluster resource group name - SQL Server (SQL1)

- next

Cluster Disk Selection

- select both of your cluster disks for data and logs

- next

Cluster Network Configuration

- uncheck DHCP and put in an available non-DHCP address

- next

Cluster Security Policy

- select Use service SIDs (recommended)

- next

Server Config

- create a service account in AD obxClusterService

- use obxbill\obxClusterService

- next

Database Eng Config

- select mixed mode

- specify your sa password

- click add current user

- click Data Directories tab, make sure you're using the correct drive for the type of db file - i.e. R:\Data and L:\Logs and R:\Backup, etc, etc

- next

Analysys Services Config

- click Add current user

- click Data Directories tab, i.e. R:\OLAP\Data, L:\OLAP\Log, R:\OLAP\Temp and R:\OLAP\Backup

- next

Reporting Services Config

- install but do not configure

- next

Error Reporting

- next

Cluster Installation Rules

- all passed - hit next

Ready to Install

- click install, go have a drink and a smoke now.

- maybe call your mom to let them know you passed the CISSP Exam...

- think about what to have for dinner

- go water some houseplants

- decide that a potbelly samich sounds easy enough

Complete

- close

now go to the obxNode04 and start the SQL install just like you did here

- setup.exe - Installation > Add node

Setup Support Rules

- all passed - ok

Prod Key - next

EULA - accept - next

Setup support files - install

Setup Support Rules

- all passed - next

Cluster node config

- select your SQL1 instance

- next

Service Accounts

- enter the password for the service acct you created earlier

- next

Error Reporting

- next

Add Node Rules

- passed

- next

Ready to Add node

- click install

Add Node Progress

- if you havent gone to go get dinner by now.  It's probably a good time. :)

- next

Complete

- success! - close

okie dokie - test your failover cluster by moving the SQL1 application, etc, etc and now go eat sandwich and watch Jeopardy or somethin.

Windows 2008 R2

1. Create vm with 1gb ram, 12gb hd, with Win2008R2 64bit iso and run


2. Activate Windows with PID


3. Update Time Zone


4. Update computer name and join domain (don't reboot just yet!)


5. Enable Remote Desktop


6. Turn off Windows Firewall for Domain, Home and Public
   
   
   
   1. Think about it. This server is in the green zone. And it you wanna have Symantec CSP installed, you eventually want this off anyway.
   
   
   
   


7. Install VMWare Tools


8. Shut down the VM


9. Reconfig the VM to have only 512mb RAM... yes, thats right folks! Squeeze-em'!


10. Start the VM, and now RDP straight to the box via either the name or IP


11. Start > Admin Tools > iSCSI initiator - click yes to turn the service on


12. Put the IP address of the OpenFiler Server in the Target box on the first tab > click Quick Connect


13. Connect to each of the disk resources that are going to be clustered (quorum, data, logs)


14. Click OK


15. Open Disk Manager and bring each disk online


16. Then give them the same drive letter as they are on the other node(s)


17. Open the Initial Configuration Tasks > Add Features > Select Failover Clustering


18. Click Next > click Install > click Close


19. Start the Failover Manager


20. Click Validate Configuration > Add the current server name > click Add


21. Enter the name of another Windows 2008 R2 Ent x64 VM that is configured the same way up to this step.


22. Click Next, Run all test > click Next > Confirmation click Next > Click View Report


23. Create a new cluster > give it a name > give it an IP address > click Next


24. Confirmation click Next > Summary Success! click Finish


25. Shut down each node - bring one node online and then bring the other one online.  Reboot each node to test failover of the disk resources.


26. now you can install SQL 2008 R2 as a cluster

Stop whining list

1. FreeNas...


2. Windows 2008 R2 2 node Cluster build


3. IIS 7.5
   
   
   
   1. php.iis.net
   
   
   2. WordPress 3.0 Post Setup
   
   
   3. mySQL - with phpmyadmin
   
   
   
   


4. SQL 2008 R2 Enterprise cluster build
   
   
   
   1. Majority node set with cluster, witness server
   
   
   2. Shared disk with quorum from iSCSI Target from FreeNAS
   
   
   
   


5. Self-Signed certs (SSL)


6. ISA - 443 to 80


7. RDP default port add/change - entry on http://d.patrickoneill.com/?p=83


8. MOSS 2007 to MOSS 2010 upgrade/migrate


9. get patches for Mom's computer :)

Virtual Domain Controllers

OK - my domain has 2 Domain Controllers that are physical (real servers).  I'm tired of the noise and space footprint in my office.  So, I've decided to create 2 new virtual machines (DC03 and DC04), promote them to domain controllers, move the roles over to them and then demote the old domain controllers (DC01 and DC02). However, when I tried to just DCPromo them, I got an error message:

The version of the ActiveDirectory schema of the source forest is not compatible with the version of the Active Directory on this computer

Resolution: http://support.microsoft.com/kb/917385

Here's my basic steps:

• Create 2 VMs with Windows 2003 Standard R2 x86 OS


• on DC01, copy CMPNENTS\R2\ADPREP from disk 2 of Windows 2003 STD R2


• Open command prompt






ADPrep /ForestPrep




Warning message will appear. As long as all DCs are 2003 and up, type C, hit ENTER




Wait.......




When completed, log off DC01






• Log onto DC03, Run DCPromo. When completed, reboot and repeat on DC04.


• Install DNS role to new DC03 and DC04. Validate all DNS Properties of the DNS and Forward lookup settings are the same between DC01 the new DC03 and DC04 DNS servers


• In stall WINS on DC03


• Install Remote Access VPN on DC03


• Install DHCP on DC03 (dont forget to Authorize it when you're done)

w32Time

Couple of good articles on this:

Set your DCs for this:

http://support.microsoft.com/kb/816042

And set your members to NT5DS

http://technet.microsoft.com/en-us/library/bb490845.aspx

Catch All Exchange 2007

http://catchallagent.codeplex.com

Installing SQL 2008 in a 2 node cluster

Woo Hoo! :)

Below are the basic steps from SQL 2005,  as I perform the actual installation for my new SQL 2008 cluster, I'll replace the steps and stuff :)

Here's a link to the SQL 2008 cluster installation:
******************************************************

Prerequisites for SQL 2008 cluster installation:

1. Add\Remove Programs > Windows Components > Application Server


2. select - Enable asp.NET


3. select - Enable network COM+ access


4. select - Enable network DTC access


5. select - Internet Information Services (IIS)


6. Start > Run > Services.msc


7. Distributed Transaction Coordinator - set to Manual


8. HTTP SSL - set to Automatic


9. Start > Run > cmd > iisreset


10. Install Windows 2003 Server SP1


11. Install configure .NET Framework 3.5

6.1 Default Instance SQL Installation
1. On the SQL Server 2005 Disk1 folder, run Setup.exe to begin the installation.
2. At the End User License Agreement page, accept the license and click Next.
3. At the Installing Prerequisites page when it says Click Install to continue, click Install and when done click Finish.
4. At the Welcome to the Microsoft SQL Server Installation Wizard, click Next.
5. At the System Configuration Check page after the check completes, verify there are no errors and click Next.
6. At the Registration Information page, enter your name and company name click Next.
7. For Components to Install, select SQL Server Database Services, Create a SQL Server failover cluster, Notification Services, Integration Services and Workstation Components…
- Click Advanced.
- Expand Client Components.
- Select to have Notifications Services, Integration Services, and Client Components installed completely to the D:\ drive and click Next.
11. Once each component has been specified to install to the D:\ drive of the server, click Next.
12. For the instance name of the first instance, leave it set to Default instance and click Next.
13. For the Virtual Server Name – enter the name of your virtual Server name for the default instance of SQL on the MS Cluster and click Next.
14. For Virtual Server Configuration, Network to use, enter Primary For the IP Address, enter xxx.xxx.xxx.xxx and for the Network subnet, enter 255.255.255.0 , click Add, and then click Next.

15. For Cluster Group Selection, select the group that contains the drive letter(s) you configured for your SQL data files and click Next.
16. For Cluster Node Configuration, add the available nodes to the selected nodes and click Next.
17. For Remote Account information, enter credentials for a user that has administrator privileges for the system and click Next.
18. For Service Account, enter the credentials for the SQL Server Service Account and click Next.
19. For the Domain Groups for Cluster Services enter your AD Service Accounts Group click Next.
20. For Authentication Mode, select Mixed Mode enter a strond password and click Next.

21. At the Collation Settings page, leave the default settings and click Next.
22. At the Error and Usage Settings, leave the default settings and click Next.
23. At the Ready to Install page, click Install
24. You can view the progress of the installation by selecting/changing the Node on the Setup Progress window.  Once setup has completed, click Next.
25. At the Completing Microsoft SQL Server 2005 Setup page, click Finish.

Creating a Windows 2003 Ent cluster with OpenFiler

Q. Do I need to do anything special when configuring an iSCSI Cluster?
A. Take the following configuration settings into consideration when using the MS Software Initiator:

1. Set all clustered volumes as "Persistent Bindings" to ensure they are remapped if the node is rebooted.


2. Set "Bind Volumes" for all clustered disks to ensure they are fully mounted by the iSCSI service before the Cluster Service attempts to bring them online.


3. Ensure you are using Microsoft iSCSI Software Initator 2.0 or above.


4. Make sure your Quorum drive is at least 500MB

Now! :)

Start up the Cluster Admin tool, File > New > Cluster

1. Welcome Screen - click Next


2. Cluster Name and Domain - select your domain from the drop and type in a new name for your cluster (I called mine obxCluster02)


3. Computer Name - type in the name of the server to be the first node


4. blah blah blah from here enjoy :)

Wordpress behind ISA

1. On ISA, Create Access rule to allow internal networks access external networks


2. On ISA, set your firewall rule. On the To tab, set the proxy setting to Requests appear to come from original client


3. On the Web Server, set the default gateway to the ISA server IP address.


4. Vwalah! - now you can do things like have clog ratings from each unique ip address, etc AND still download and install themes and plugins from the Wordpress dashboard.

Enjoy :)