Google Stuff

Google’s YouTube Channel
http://www.youtube.com/user/Google#p/a

Getting Started with Google Docs


Embed Google Presentation to a website


Insert Videos into Google Presentation


Creating Google Sites


Creating Google MyMaps

Sample Screencast posting using Jing

this is a test only

MOSS 2010 and Project Server 2010 install instructions

MOSS 2010

run spash.html
install prerequisits
Server Farm
select complete install - not standalone
follow this blog for service accounts
in AD, create a moss2010_admin domain account
and create a moss2010_farm domain account
give email address of moss2010_admin@domain.com to both accts!
Add these account to the local Admins group of the farm servers
login to the farm servers as the moss2010_admin account
on the SQL Server - create a new user in SQL as domain\moss2010_admin - grant dbcreator and securityAdmin

******
USE [master]
GO
CREATE LOGIN [Domain\moss2010_admin]
FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GO
EXEC master..sp_addsrvrolemember
@loginame = N'domain\moss2010_admin',
@rolename = N'dbcreator'
GO
EXEC master..sp_addsrvrolemember
@loginame = N'Domain\moss2010_admin',
@rolename = N'securityadmin'
GO
*******

config wizard

- Welcome- next
- Services warning - click Yes
- Connect to a server farm, select create new server farm, click next
- Database settings
- - Database server: obxSQL0801\SQl1
- - DB Access Account: domain\moss2010_farm
- Farm Security Settings
- - Passphrase - give it a pwd, next
- Centrl Admin Web App
- - no specific port, NTLM, Next
- Completing config Wiz, verify settings, next
- Config Successful, finish

Central Admin - Wizard

- Use existing managed account (not a new one, should be your moss2010_farm account), next
- Wait here... 5 min later... just a few more minutes :)
- New Top Level Site, create a site with a good name, description and select Team Site, click OK
- Wait here again, maybe go have a smoke-break or somethin.
- Now configure an alternate access mapping for something coming from outside your intranet. Mine was http://servername as the default. I edited it and added an Internet Zone URL of http://www.WhatEverYourExternalDomainNameIs.com, click Ok
- - think of it as the old host header files
- then on your local machine notebook or whatever, edit your host file to point www.WhatEverYourExternalDomainNameIs.com to your MOSS2010 Farm Server's IP address.
- - open a CMD window, type in edit c:\windows\system32\drivers\etc\hosts
- - add an entry like below:
- - - 192.168.xxx.xxx www.WhatEverYourExternalDomainNameIs.com
- Exit the file, Save and then do an ipconfig /flushdns
- open a browser - go to - www.WhatEverYourExternalDomainNameIs.com
- you may find that you need to go back into Central Admin and Add your actual domain user account to the Site Collection Admins for your new web app.

Project Server 2010

Login to Farm server as domain\moss2010_admin
run spash.html
click Install software prerequisits
- Welcome, next
- EULA, Accept, next
- Installation Complete, Finish
Click Install Project Server
- Enter PID, Continue
- EULA, Accept, Continue
- File Location, click Install Now
- Run Config Wizard, Close
Config Wizard
- Welcome, Next
- Services reset warning, click Yes
- Database Server, DB Name, click Next
- go have a smoke break
- Config Successful, click Finish
**Browser Opens
- http://servername:portnum/_admin/adminconfigintro.aspx?scenarioid=adminconfig&welcomestringid=farmconfigurationwizard_welcome&isupgrade=true
- Login as domain\mosss2010_admin
- click Start the Wizard
- Service Account and Services, leave default and click Next
- wait here or there, maybe order some carry-out chinese
- Create a new Top-Level Web App -
- - Web Site Address, select /sites/, name Projects
- - Template - Team Site, click OK
- login to the site using your domain/moss2010_admin account
- Open Site Actions, add your real domain\user account to the Site Collection Administrators

Then re-run the MOSS config Wizard to integrate MOSS and Project Server

Install and configure Project Server 2010
http://technet.microsoft.com/en-us/library/ee662109.aspx

Create a PWA site in your web app
http://technet.microsoft.com/en-us/library/ee662105.aspx

Configure Reporting
http://technet.microsoft.com/en-us/library/ee662106.aspx

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 3.0 Setup

WordPress 3.0 Setup

1. Install WordPress with Web Platform Installer


2. Useful WordPress Setting Changes
   
   
   
   1. Settings > Writings > Remote Publishing > XML-RPC Checkbox and Save Changes
   
   
   2. Settings > Discussion > Other comment settings > Automatically close comments older than 14 days Checkbox and Save Changes
   
   
   3. Settings > Privacy > Site Visibility > I would like to block search engines, but allow normal visitors Select and Save Changes
   
   
   4. Settings > Permalinks > Custom Settings > Custom Structure > Enter /%postname% in the text box for SEO
   
   
   
   


3. Useful WordPress Plugins
   
   
   
   1. Plugins > Add New > Enter Configure SMTP and Click Search Plugins > find Configure SMTP and Install Now > Actions: Activate Plugin
      
      
      
      1. Settings > SMTP > Check Send e-mail via GMail? and enter a real gmail address > Save Changes
      
      
      
      
   
   
   2. Plugins > Add New > Enter Static Toolbar and Click Search Plugins > find Static Toolbar > Actions: Activate Plugin
   
   
   3. Plugins > Front-end Editor > Actions: Activate Plugin
   
   
   4. Plugins > Exclude Pages from Navigation > Actions: Activate Plugin
   
   
   5. Plugins > Featured Content Gallery > Actions:  Activate Plugin (maybe?)
   
   
   6. Plugins > Add New > Enter WordPress File Monitor and Click Search Plugins > find WordPress File Monitor > Actions: Activate Plugin
   
   
   7. Plugins > Add New > Enter Sharedaddy and Click Search Plugins > find Sharedaddy > Actions:  Activate Plugin
   
   
   8. Plugins > Add New > Enter Postie - install and activate
      
      
      
      1. configure with email address, ssl imap, imap.gmail.com, only admins will be able to post until further configs are completed
      
      
      
      
   
   
   
   


4. Useful WordPress Widgets to configure
   
   
   
   1. SiteMeter
      
      
      
      1. Appearance > Widgets > Drag a Text Box Widget to a Widget Area > Paste appropriate HTML from sitemeter.com
      
      
      
      
   
   
   2. Tag Cloud
      
      
      
      1. Appearance > Widgets > Drag a Tag Cloud Widget to a Widget Area > Taxonomy:  Categories
      
      
      
      
   
   
   3. Twitter
      
      
      
      1. Appearance > Widgets > Drag a RSS Widget to a Widget Area
         
         
         
         1. RSS Feed URL:  http://twitter.com/statuses/user_timeline/11893692.rss
         
         
         2. Uncheck Display Item Content
         
         
         3. Uncheck Display Item Author If Available
         
         
         4. Check Display Item Date and Save
         
         
         
         
      
      
      
      
   
   
   4. Links
      
      
      
      1. Appearance > Widgets > Drag a Links Widget to a Widget Area
      
      
      
      
   
   
   
   

WordPress Installed on IIS 7.5 with SQL 2005 or 2008

Here is a quick layout of instructions in installing WordPress on Windows 2008 R2 IIS 7.5 with SQL 2005 or 2008

Download wp-sqlsrv-2.9.2-beta-0.8.8.zip This is a special version of Wordpress that allows you to connect to a SQL server... or cluster... :) why not?!

Unzip files to C:\inetpub\WPOnSQL

Open IIS Mgr -

Open your Web Platform Installer > Web Platform > Database > Customize > Microsoft Drivers for PHP for SQL Server 2.0. Install this thing before you create your site.

Create new site

Enter Site Information
Website:  New Web Site
WordPress application name:  /
Web Site Name: blog.boneyard.org
Physical Path:  c:\inetpub\blog.boneyard.org
IP Address:  All Unassigned
Host Name:  wponsql.boneyard.org
Click OK

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

Go to your SQL box, open SQL Mgmnt studio and create a new database. Then create a SQL user that has dbo privs on that database. Then from your IIS, you can test your connection using ODBC manager.

Open site in a browser

The wp-config file will be missing, so let the site walk you through providing it with the database servername, database, and sql credentials

Create Configuration File > Lets Go >

Database Name: TEST

Username: sqlgod

Database Host: databaseservername\instancename

Database Type: SQL Server Using PHP Driver

Table Prefix: wp_

Click OK - the click Run the Install
Blog Title:  Wordpress on SQL Blog
Your E-mail:  admin@boneyard.org
Click Install WordPress

Login to Wordpress

Logout and do the following

http://blog.obxbill.com/?p=582

Click Dashboard and then Updates

An updated version of WordPress is available.
Click Update Automatically
After you see "WordPress updated successfully", click Go to Dashboard

WordPress 3.0 Installed on IIS 7.5 with mySQL

Here is a quick layout of instructions in installing WordPress on Windows 2008 R2 IIS 7.5

From IIS

Web Platform Installer
New Web Application box
Select WordPress
Click Install
Click I Accept at the EULA
Enter Site Information
Website:  New Web Site
WordPress application name:  /
Web Site Name: blog.boneyard.org
Physical Path:  c:\inetpub\blog.boneyard.org
IP Address:  All Unassigned
Host Name:  blog.boneyard.org
Click Continue

Enter Application information
Choose Your database:  MySQL
Create New database
Database Administrator:  root
Database Name:  blogboneyardorg
Finished
Exit

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

Open site in a browser
Site Title:  Boneyard Blog
Username:  admin
Your E-mail:  admin@boneyard.org
Click Install WordPress

Login to Wordpress

Logout and do the following

http://blog.obxbill.com/?p=582

Click Dashboard and then Updates

An updated version of WordPress is available.
Click Update Automatically
After you see "WordPress updated successfully", click Go to Dashboard

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.

FreeNAS - This thing rocks.

FreeNAS is a free network-attached storage server OS. Personally, I like to use it as a VM with 256 MB RAM (higher if your going to do RAID5, then you want 512, and if you're thinking ZFS then, better give a gig) and an 8GB thin provisioned VHD on one of my ESXi servers. You could probably get away with an even smaller VHD drive for the OS. Supposedly only 128MB. I figure, I'll give it a thin-provisioned disk and if it ever needs it, it'll grab it then. Minimum Hardware Requirements

1. Download the ISO file of the version you want from here


2. Create and start a new VM with 8gb thin vhd, 256 mb ram and give it a name like obxFreeNAS01 with your iso file attached.


3. Once it's started, choose to install FreeNAS on the local 8gb thin vhd.


4. Then configure your IP address as DHCP first... then let it initialize.  Now, I know you don't want a stupid DHCP address on that thing. because you don't want your iSCSI initiators out there losing a potentially very important connection to it's drive. But trust me on this...


5. Test a regular ol web browser and point it to the DCHP address that it was assigned.  Just to make sure you get a login at all.


6. Shutdown your FreeNAS vm. Now configure a few new thin-provisioned VHDs for this VM.  Make a 5gb, 10gb and a 20GB one.  Later we'll use them for things like a quorum, data drive and a log drive for a SQL 2008 R2 Failover Cluster :)


7. Start up your FreeNAS vm.


8. Configure a static IP address for the FreeNAS... let it initialize.


9. Now, go open a browser and make sure that the login screen for FreeNAS comes up ok.


10. login with username admin and password freenas Once you're in, you should go update the default password to something else and also create yourself a new user account with admin privs.


11. Next to come... the steps to create iSCSI Targets for your Windows 2008 R2 nodes to use for a Failover Cluster.


12. Disks > Management > click the + link, select a disk you want to carve for your cluster (it'll be something like da1)


13. Give it a description, like Logs. Leave it Unformatted and click Add


14. Do the same for all of the vhds that you created for your cluster. I've got 3. Quorum of 5gb, Data of 20GB and Logs of 10GB.


15. Disks > Format > Format UFS for each of your disks, give them a Volume label that matches your descriptions from the previous steps.  There's many ways to skin this cat.  This is simply my little method.


16. Disks > Mount Points > click the + link. Give it a mount point name and description. I'm boring, I just used the same names I used for the respective volume names and disk descriptions. click Add.
    
    
    
    1. Oh yeah... you might notice that things get stuck in Modifying status... uh... don't forget to click APPLY CHANGES.... it's a sneaky little button at the top of the page in a few places.
    
    
    
    


17. Services > iSCSI Target > Settings > Set your Base Name...
    
    
    
    1. I'm using iqn.2007-09.jp.ne.peach.obxFreeNAS01
    
    
    
    


18. Services > iSCSI Target > Initiators> create an initiator for your own subnet.
    
    
    
    1. (i.e. 192.168.1.0/24)
    
    
    
    


19. Services > iSCSI Target > Portals > use  the static IP address of your FreeNAS VM.
    
    
    
    1. something like this 192.168.1.58:3260
    
    
    
    


20. Services > iSCSI Target > Targets > create an extent file for each of your disks
    
    
    
    1. mine looks like this: Extent name - Data0, Type - File, Path - /mnt/Data/data.file, File Size - 20Gib, Comment - Data
    
    
    2. now! Create a Target for that extent file we called Data0 and give it a Target Name of Data0
    
    
    3. Click Add at the bottom, now click Apply Changes at the top.
    
    
    
    


21. ok - now you're ready to build a Windows 2008 R2 cluster.  Just fire your nodes up and use the local iSCSI initiator to connect to your disks. Bring em online, initialize them, format them, give them drive letters and give them a volume name.

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 :)

Users in SharePoint with email addresses not associated with the domain

This is a pretty easy one actually. 

1. Start > Run > dsa.msc (this opens Active Directory Users and Computers)


2. Select the user. On the General Tab, change the email address to an email address that your domain isn't managing (i.e. @yahoo.com, @gmail.com, etc, etc). Click OK


3. Open SharePoint Central Admin console. Click the SSP link off of the Home page of Central Admin


4. Login (duh).


5. Under User Profiles and My Sites > Click User Profiles and Properties


6. Click Start Full Import


7. After the import is completed, you should view the target user's profile and remove any Proxy addresses.

Next, if the user has already been granted access to your MOSS Web Application, you will need to remove the user and then re-add the user back into their original permissions. Then, when you go to view the user's profile details, they will show up with the user's new email address.

To put the entire SQL server into single user mode

This is for SQL2005, for SQL 2008, you will need to change the directory where the sqlservr.exe file is located.

Open Cluster Admin - stop SQL services

open cmd prompt and type (or copy/paste) the following:

cd "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn"

sqlservr.exe /s SQL1 /c /m /T3608

- you will see a bunch of stuff fly by on the cmd window, this is normal

start SQL Management Studio

Click CANCEL! on the connection prompt

Click New Query - then select your database from the drop list (it's right under the New Query button)

Paste in your DB reindex t-SQL script in the query window and execute

Set a database into Single User Mode

ALTER DATABASE [URSTUPIDDATABASE] SET MULTI_USER WITH NO_WAIT

ALTER DATABASE [URSTUPIDDATABASE] SET SINGLE_USER WITH NO_WAIT

or

EXEC sp_dboption 'URSTUPIDDATABASE', 'single user', 'false'

EXEC sp_dboption 'URSTUPIDDATABASE', 'single user', 'true'

t-SQL to allow comments and ping backs on all your posts

If you want to update all of your posts in your Word Press blog site from closed commentsand closed pingbacks, then you can run this update script to update all of your posts to allow comments and pingbacks. Log in to your PHPMyAdmin where your database for your site lives, select the database, then select Query and insert the following, then click Go. :)

UPDATE wp_posts
SET Comment_Status = 'open',Ping_Status = 'open'
WHERE ID > 0

NOTE: Now, sometimes, when these SQL queries are placed in block-quotes, the single quotes get all weird and you might have to re-type them.

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)

Moving the System databases for SQL 2005 on a cluster

Background

Best practices for SQL configuration recommend moving system databases, particularly the TempDB, to a separate drive.  On a cluster, this drive must be a shared cluster resource that is, like all drives supporting the SQL instance, a dependent cluster resource.  While there is no need to separate out the data and log files for system databases, the following instructions will assist in moving system files together to a separate clustered drive.  In the examples below, assume E:\ is a clustered drive resource which can be replaced with whatever specific drive is designed for each particular instance.

1.0 Moving Model Database Files

1. In Cluster Admin, shut down SQL Server and SQL component cluster resources.


2. Navigate to a command prompt on the active node and start the SQL server using startup parameters:

"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" –s<instance name> –c –m –T3608

NOTE:  Cluster resources for drives, virtual server, and IP address must be online. Also, for more information on the startup parameters, see http://technet.microsoft.com/en-us/library/ms190737.aspx and http://technet.microsoft.com/en-us/library/ms188396.aspx

1. Ensure the SQL Browser has been restarted.


2. Open SQL Server Management Studio but cancel the login dialog


3. Close the Object Explorer window.


4. Click on New Query and log in as Admin (i.e., ADMIN:ServerName\InstanceName) using sa account (assuming the sa account is system administrator account).


5. Use the following query:

use master
go
sp_detach_db 'model'
go

1. Move the Model.mdf and Modellog.ldf files from the current location to the desired location.


2. Reattach the model database by using the following commands:

use master
go
sp_attach_db 'model','E \model.mdf','E:\Sqldata\modellog.ldf'
go

(NOTE:  Replace the filepath above with the new location of the files.)

10.  Close SQL Server Management Studio

11.  Shut down SQL by typing Ctrl + C at the command prompt where you started SQL.

12.  Bring SQL Resource online in Cluster Administrator.

13.  Open SQL Server Management Studio (you should be able to log in normally as you are no longer in single-user mode).

14.  Verify the location of the model files by running the following query:

use model
go
sp_helpfile
go

2.0 Moving MSDB Database Files

1. In Cluster Admin, shut down SQL Server and SQL component cluster resources.


2. Navigate to a command prompt on the active node and start the SQL server using startup parameters:

"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" –s<instance name> –c –m –T3608

NOTE: Cluster resources for drives, virtual server, and IP address must be online.

1. Ensure the SQL Browser has been restarted.


2. Open SQL Server Management Studio but cancel the login dialog


3. Close the Object Explorer window.


4. Click on New Query and log in as Admin (i.e., ADMIN:ServerName\InstanceName) using sa account (assuming the sa account is system administrator).


5. Use the following query:

use master
go
sp_detach_db 'msdb'
go

1. Move the Model.mdf and Modellog.ldf files from the current location to the desired location.


2. Reattach the model database by using the following commands:

use master
go
sp_attach_db 'model','E \msdbdata.mdf','E:\Sqldata\msdblog.ldf'
go

(NOTE:  Replace the filepath above with the new location of the files.)

10.  Close SQL Server Management Studio

11.  Shut down SQL by typing Ctrl + C at the command prompt where you started SQL.

12.  Bring SQL Resource online in Cluster Administrator.

13.  Open SQL Server Management Studio (you should be able to log in normally as you are no longer in single-user mode).

14.  Verify the location of the model files by running the following query:

use msdb
go
sp_helpfile
go

3.0 Moving Master Database Files

1. From the Start menu, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager


2. In the SQL Server Services node, right-click the instance of SQL Server (for example, SQL Server [MSSQLSERVER]) and select Properties


3. In the SQL Server (instance_name) Properties dialog box, click the Advanced tab.


4. Edit the Startup Parameters values to point to the planned location for the master database data and log files, and click OK.  Moving the error log file is optional.


5. The parameter value for the data file must follow the -d parameter and the value for the log file must follow the -l parameter.  The following example shows the parameter values for the default location of the master data and log files.

-dC:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

1. If the planned relocation for the master data and log files is E:\SQLData, the parameter values would be changed as follows:

-dE:\SQLData\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\ERRORLOG;-lE:\SQLData\mastlog.ldf

1. Stop the instance of SQL Server by right-clicking the instance name and selecting Stop


2. Move the master.mdf and mastlog.ldf files to the new location.


3. Restart the instance of SQL Server

10.  Verify the file change for the master database by running the following query:

SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files
WHERE database_id = DB_ID('master');
GO

4.0  Moving TempDB Database Files

1. Determine the logical file names of the tempdb database and their current location on the disk:

SELECT name, physical_name AS CurrentLocation
FROM sys.master_files
WHERE database_id = DB_ID(N'tempdb');
GO

1. Change the location of each file by using ALTER DATABASE

USE master;
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = 'E:\SQLData\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME = 'E:\SQLLog\templog.ldf');
GO

1. Stop and restart the instance of SQL Server


2. Verify the file change:

SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files
WHERE database_id = DB_ID(N'tempdb');

1. Delete the tempdb.mdf and templog.ldf files from the original location.


2. Add additional tempDB files:

ALTER DATABASE tempdb
ADD FILE (NAME = tempdev2, FILENAME = 'X:\tempdb2.mdf', SIZE = 256);
ALTER DATABASE tempdb
ADD FILE (NAME = tempdev3, FILENAME = 'X:\tempdb3.mdf', SIZE = 256);
ALTER DATABASE tempdb
ADD FILE (NAME = tempdev4, FILENAME = 'X:\tempdb4.mdf', SIZE = 256);
GO

NOTE: Replace the path and filename with appropriate target names.

Add as many files as there are processors per MS Best Practices.  The final number is discretionary based on the demand model for the system.

Restart the server and verify the functionality and location of tempDB:

use tempdb
go
sp_helpfile
go

Note: don't forget to delete the old tempdb MDF and LDF files. SQL won't do it...

Updating the TEMPDB

Here's a quick/dirty little script to update your tempdb for SQL to 5GB for the tempdev (tempdb.mdf) file and 512MB for the templog (templog.ldf) file while at the same time turning off Auto Growth.

USE [master]

GO

ALTER DATABASE

[tempdb]

MODIFY FILE

(NAME = N'tempdev', SIZE = 5242880KB , FILEGROWTH = 0)

GO

ALTER DATABASE

[tempdb]

MODIFY FILE

(NAME = N'templog', SIZE = 524288KB , FILEGROWTH = 0)

GO

The restart your SQL Server Agent and SQL Server Services. Mine is on a cluster with the instance named SQL1.  If you are running on an MS Cluster, then you should probably do this via the Cluster Administrator console because even though the services may be online, the cluster admin console may report them to be in a failed state.

net stop SQLAgent$SQL1 & net stop MSSQL$SQL1

net start MSSQL$SQL1 & net start SQLAgent$SQL1

And yes, you can run a single command with that little ampersand (&) thingy there. :)

Here's an example of setting a TempDB with the following:

mdf file at 15GB, max size of 17.5GB, and growth at 10%

ldf file at 1.5GB, max size of 1.8 GB, and growth set to 10%

USE [master]
GO
ALTER DATABASE [tempdb]
MODIFY FILE ( NAME = N'tempdev',
SIZE = 15728640KB ,
MAXSIZE = 18350080KB,
FILEGROWTH = 10% )
GO
ALTER DATABASE [tempdb]
MODIFY FILE ( NAME = N'templog',
SIZE = 1572864KB ,
MAXSIZE = 1835008KB,
FILEGROWTH = 10% )
GO

Special note: If you copy/paste the code from the block-quotes above, and then try to run them in SQL Management Studio, you might notice them failing.  Try updating the single quotes from  around the file names, tempdev and templog.

Zen of Attraction

If Less Is More, Then Nothing Is Everything

1. Promise Nothing

Just do what you most enjoy doing.

Hidden benefit: You will always over-deliver.

2. Offer Nothing

Just share what you have with those who express an interest in it.

Hidden benefit: Takes the pressure off of wanting other people to see you as valuable or important.

3. Expect Nothing

Enjoy what you already have. It’s plenty.

Hidden benefit: You will realize how complete your life is already.

4. Need Nothing

Just build up your reserves and your needs will disappear.

Hidden benefit: You boundaries will be extended and filled with space.

5. Create Nothing

Just respond well to what comes to you.

Hidden benefit: Openness.

6. Hype Nothing

Let quality sell by itself.

Hidden benefit: Trustworthiness

7. Plan Nothing

Take the path of least resistance.

Hidden benefit: Achievement will become effortless.

8. Learn Nothing

Let your body absorb it all on your behalf.

Hidden benefit: You will become more receptive to what you need to know in the moment.

9. Become No One

Just be more of yourself.

Hidden benefit: Authenticity.

10. Change Nothing

Just tell the truth and things will change by themselves.

Hidden benefit: Acceptance.

Free/Busy Problems Exchange 2007 and Outlook clients

http://wadingthrough.wordpress.com/2006/07/31/unable-to-clean-local-freebusy-information/

http://forums.msexchange.org/m_1800424559/mpage_1/key_/tm.htm#1800424559

How to reset system folders in Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;822444

How to reset system folders in Exchange Server 2007
http://technet.microsoft.com/en-us/library/bb331972(EXCHG.80).aspx

Eseutil /Y Copy File Mode on non-Exchange Server

The ability of Eseutil to copy large files is a capability introduced in Exchange Server 2003 that has been imported from ESEFile. The copy file mode is optimized to copy very large files efficiently. You can use the switch to copy a database, streaming file, or log file. However, the mode is not suited as a general purpose copy utility.

You can use the Eseutil /Y switch to copy a database, streaming file, or log file. For best speed and stability, you should run Eseutil /Y from a local command prompt on the copy destination server rather than from an intermediate location

From Server 2

ESEUTIL /Y \\server1\d$\priv1.edb /D\\server2\d$\priv1.edb

NOTE! Don't forget to provide the file name at the destination. Otherwise, you will get an error message.

Copying c:\program files\exchsrvr\mdbdata\priv1.edb to c:\Foldername

FAILURE: CreateFile: Access is denied

Eseutil /D Defragmentation Mode
Eseutil /P Repair Mode
Eseutil /C Restore Mode
Eseutil /R Recovery Mode
Eseutil /G Integrity Mode
Eseutil /M File Dump Mode
Eseutil /K Checksum Mode
Eseutil /Y Copy Mode

To run ESEUTIL on a non-Exchange system, follow these steps:

1. Copy Eseutil.exe, Ese.dll, Jcb.dll, Exosal.dll, and Exchmem.dll from Exchange Server's Exchsrvr\bin folder to a folder on the non-Exchange server.


2. Run the desired ESEUTIL commands against the copied database.

Adding the Knowledge Base site template for MOSS 2007

stsadm -o addsolution -filename C:\Bits\KnowledgeBase.wsp

stsadm -o deploysolution -name KnowledgeBase.wsp -allowgacdeployment -immediate

WSS Central Administration site.
Click the Operations tab, and
then click Solution management under global configuration.

After all the solutions are marked Globally Deployed,

run iisreset from the command line.
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx

Transfer\Move FSMO Roles

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

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

How to host multiple web-sites on XAMP

Edit C:\xampp\apache\conf\httpd.conf
- yes... there are more lines in that file, but these are the ones you need to edit... :)

ServerName *:80

#DocumentRoot "C:/xampp/htdocs"

#<Directory />
# Options FollowSymLinks
# AllowOverride None
# Order deny,allow
# Deny from all
#</Directory>

#<Directory "C:/xampp/htdocs">
# Options Indexes FollowSymLinks Includes ExecCGI
# AllowOverride All
# Order allow,deny
# Allow from all
#</Directory> 

Edit C:\xampp\apache\conf\extra\httpd-vhosts.conf
- ok - just kinda follow the logic for each website... and place your web files in the right directory... or else...!

<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot "C:/xampp/htdocs/FolderForWhateverSite"
ServerName www.whatever.com
##ServerAlias www.whatever.com
ErrorLog "logs/error.log"
CustomLog "logs/error.log" combined
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
<Directory "C:/xampp/htdocs/FolderForWhateverSite">
Options Indexes FollowSymLinks Includes ExecCGI
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

Then go to command prompt:

net stop apache2.2 & net start apache2.2

Ever wanna clear your SSL Cert Cache?

certutil -urlcache * delete

Free Disk Utilities

http://www.freebyte.com/filediskutils/

Installing Exchange 2007 - basics

Install Windows 2003 Ent x64

Install all Windows Updates - reboot

Install IIS

Check for more Windows Updates - reboot

Run Exchange 2007 setup.exe

MailFlow Settings - <Your old Exchange 2003 Server Name>

Readiness Check - all green? - click install

click yes - reboot - run the setup.exe again to Get Critical Updates for Exchange 2007

- mine found Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162)

install AdminPack

install Resource ToolKit

reboot

Open IIS - change directory security so that it does not require 128-bit encryption

Open Exhcange MMC - Server Config > Client Access - Properties of OWA

- - set the internal and external URLs - make sure that the S from the https has been removed.

- - The internal one I set for http://servername.domain.net/owa

- - The external one I set for http://owa.publicdomain.com/owa

After this part, you're ready to configure your proxy server to handle the incoming traffic to OWA and direct it to your new Exchange Server.

How to configure anti-spam agents Exchange 2007

Link HERE!

By default,  only the Journaling and Transport Rule agents are installed on the Hub Transport server role. The Anti-Spam Agent must be installed and enabled for you to use the associated transport feature. Only the agents that provide the messaging features that are designed to be deployed inside the organization are installed by default. Agents that are not installed are designed for use in the boundary network on a computer that has the Edge Transport server role installed. To view the agent configuration, run the Get-TransportAgent command in the Exchange Management Shell.

You can install the anti-spam agents on the Hub Transport server role by using the provided Install-AntiSpamAgents.ps1 script. The script is located in the %programfiles%\Microsoft\Exchange Server\Scripts folder. After you run this script, all of the anti-spam agents are installed and enabled, and the Anti-spam tab is available in the Exchange Management Console.

Open Exchange Management Shell

Set-Location "c:\program files\Microsoft\exchange server\scripts"
./install-AntispamAgents.ps1
Restart-Service MSExchangeTransport

Now, go do a Microsoft Update! This will ensure that you're running with the most recent Anti-Spam Filter Updates.

OK - back to Exchange Management Shell

get-TransportConfig

- if you'vge already configured your Intern SMTP Servers to include all of your SMTP servers that this server is going to talk to, then you're good.
- if not, then do the following:

Set-TransportConfig -InternalSMTPServers 10.0.1.10,10.0.1.11

Of course, use the IPs of your actual SMTP servers. :P

NOTE:
For all anti-spam features to work correctly, you must have at least one IP address of an internal SMTP server set on the InternalSMTPServers parameter on the Set-TransportConfig cmdlet. If the Hub Transport server on which you're running the anti-spam features is the only SMTP server in your organization, enter the IP address of that computer.

Of course, use the IPs of your actual SMTP servers. :P

Done

Exchange 2007 - sending out 25 blocked somehow?

Since, I'm using an ISP that blocks incoming ports like 80 and 25, etc., I have to work things a little differently. A friend of mine has a small datacenter and he's allowed me to use his SMTP server as a relay as well as his ISA server for proxying. So, for OWA, my ISA rule is pretty much a default Exchange OWA rule out-of-the-box with the only exception being that it's bridged on the back of the rule to port 81 on my router. Then my router forwards all port 81 traffic to my Exchange server.

Now, for some reason, my ISP also blocks port 25 in and out. Ugh,... I know... a total P.I.T.A.!!!

So, what do I do?

I run all my email through my buddy's SMTP server and Exchange via not just port 25 but also port 26. So, his router forwards all traffic from port 25 to 26 to his SMTP server (just a basic SMTP server and not an Exchange server).

So, as long as your recieving smtp server (in my case, my friend's SMTP server out there on the internet) is configured to recieve from you and it's an smtp server you control outside your network, you can fix this issue.

First - make sure your external smtp server can recieve on both port 25 and 26. And that it will allow relay of your public IP along with the domain name your using.

Then in your exchange server, set your send connector's smart-host to the public ip of that smtp server out there.

There isn't an option in the Exchange MMC to use another port other than 25. So, we will need to use the exchange shell command below:

set-sendconnector -identity "yourwackyconnectorname" -port 26

This will allow your exchange box to send your emails out on port 26 instead of port 25

Windows Installer CleanUp Utility (Office 2000, Office XP, or Office 2003)

When you are working on your computer and installing a new program, the installation suddenly fails. Now you are left with a partly installed program. You try to install the program again, but you are unsuccessful. Or, maybe you have problems trying to remove an old program because the installation files are corrupted.

Do not worry. Windows Installer CleanUp Utility might be able to help. You can use the utility to remove installation information for programs that were installed by using Windows Installer. Be aware that Windows Installer CleanUp Utility will not remove the actual program from your computer. However, it will remove the installation files so that you can start the installation, upgrade, or uninstall over.

How to make FLV files play in IIS site

how to make FLV files play in IIS site:

• Open IIS site, Properties


• HTTP Headers tab


• Click MIME Types


• Enter extension: .flv


• MIME Type: video/x-flv

MS IT 2.0 Recycle Bin Install steps

1. Run RecycleBinInstaller.msi


2. Welcome to the SharePoint Portal Server Recycle Bin Setup Wizard – click Next


3. Recycle Bin Folder location – C:\SPS_RecycleBin
   
   
   
   1. Log File location – C:\SPS_RecycleBin_Logs\LogFile.txt
   
   
   2. Action Log File location – C:\SPS_RecycleBin_Logs\ActionLog.txt
   
   
   3. Click Next
   
   
   
   

Note: The RecycleFolder location in which to store deleted Site Collection information must be configured to allow Read/Write permissions to all Authenticated Users.

1. Select Installation Folder:
   
   
   
   1. Leave the default folder location.
   
   
   2. Select Everyone for the installation option.
   
   
   3. Click Next
   
   
   
   


2. Confirm Installation – click Next


3. Installation Complete – click Close

Note: SharePoint Portal Server Recycle Bin will create a Registry entry for HKLM\SOFTWARE\Microsoft\IT\SharePoint Portal Extensions\Recycle Bin\.

1. Open IIS Manager and navigate to the Web Service Extensions


2. Right-click Web Service Extensions and select Add a new Web service extension…


3. Extension name – enter RecycleBinISAPI – click Add

10.  Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll

1. click OK

11.   Click Add – Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll

12.  Click Set extension status to Allowed – click OK

13.  Verify the new Web Service Extension is allowed from IIS Manager.

14.  Expand the Web Sites within IIS Manager.

15.  Right-click the website for YourPortalSite (Default Web Site) and select Properties

16.  Select the ISAPI Filters tab

17.  Click Add

1. Filter name – enter RecycleBinISAPIFilter


2. Executable – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll


3. Click OK

18.  Verify ISAPI Filter – right-click the website for your portal site (Default Web Site) and select Properties

1. Select the ISAPI Filters tab – verify the RecycleBinISAPIFilter Filter Name displays a green arrow in the Status column and the Priority is set to High

19.  Select the RecycleBinISAPIFilter on the Default Web Site (for your portal site) Properties dialog and click the Move up button – click OK

20.  Expand the Default Web Site (where StaffCollaborator is located).

1. Right-click the _vti_bin virtual folder and select Properties from the context menu.


2. Under Application Settings, click Configuration, and click Insert


3. Executable – enter “C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll” (don’t forget the quotes!)


4. Click OK three times.

21.  Expand the Default Web Site (where your portal is located).

1. Right-click the _layouts virtual folder, then select the Recycle folder and select Properties from the context menu.


2. Click Create


3. Application Pool – select MSSharePointPortalAppPool


4. Click Configuration – click Add


5. Executable – enter C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll


6. Extension – enter .spsrec – click OK twice.

22.  Restart IIS

23.  Open Notepad

1. Enter – Forfiles -p C:\SPS_RecycleBin -s -m *.* -d -15 -c “cmd /c del /q @path”

Note: The 15 in the command will delete all files in the path that are older than 15 days.

1. Save as RecycleBinCleaner.CMD to C:\SPS_RecycleBin_Logs

24.  Open Control Panel – create a scheduled task to run daily that will execute C:\SPS_RecycleBin_Logs\RecycleBinCleaner.CMD

1. Start time – 1AM – Run the Scheduled Task as the service account Network\SPSRecycleBinCleaner

Uninstall Process

1. Open IIS Manager from all of your IIS user web front-end servers for SPS2003


2. select Default Web Site (for for your portal site), right-mouse click and select Properties


3. Select the ISAPI Filters tab - remove the RecycleBinISAPIFilter - click OK


4. expand the Default Web site (staffcollaborator)
   
   
   
   1. select _vit_bin, right-mouse click, select Properties
   
   
   2. click Configuration
   
   
   3. Under Wildcard... - Remove the RecylceBin entry
   
   
   4. click OK - click Yes to approve - click OK twice
   
   
   
   


5. From IIS Manager - select the Web Service Extensions - select and Delete the Recycle Bin ISAPI entry


6. Control Panel > Add/Remove Programs - Select SharePoint Portal Server Recycle Bin - click Remove


7. restart IIS

SharePoint AAM Stuff

http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

Office SharePoint Server Publishing Infrastructure - Access Denied

If you don't activate Publishing Resources when you first install SharePoint (MOSS 2007), when you try and activate it later via site collection features, you might see an access denied error when activating. You can manually activivate Publishing Resources via stsadm:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>
stsadm -o activatefeature -name PublishingResources -url http://website

Operation completed successfully.

You will then be able to activate Office SharePoint Server Publishing Infrastructure.

Hard Drive Recovery Videos

This guy really knows his shit. There's a 5 part series on the anatomy of a hard drive and 4 of the main methods of recovering data from a failing hard drive.

http://www.youtube.com/user/SuperFlyFlippingA

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 :)

Configuring OpenFiler v2.3 iSCSI target server

http://www.techhead.co.uk/how-to-configure-Openfiler-v23-iscsi-storage-for-use-with-vmware-esx

Step 1: Network Access

Step 2: Create New Physical Volume

Step 3: Create New Volume Group

Step 4: Create New Volume

Step 5: Enable iSCSI Target Service

Step 6: Add iSCSI Target

Step 7: Map the LUN

Step 8: Allow access to the iSCSI Target

Ubuntu iSCSi target - 9.10

first - create an additional HD for our VM of Ubunutu

next - started VM, used gparted to format the new drive (ext2)

sudo apt-get install gparted

sudo apt-get install iscsitarget

sudo apt-get install lvm2

sudo pvcreate /dev/sdb1

Physical volume "/dev/sdb1" successfully created

sudo vgcreate -s 16M vg0 /dev/sdb1

Volume group "vg0" successfully created

http://www.howtoforge.com/using-iscsi-on-ubuntu-9.04-initiator-and-target

sudo lvcreate -L 20G -n storage_lun1 vg0

Logical volume "storage_lun1" created

sudo gedit /etc/ietd.conf

Target iqn.2010-02.net.obxbill:storage.lun1

IncomingUser

OutgoingUser

Lun 0 Path=/dev/vg0/storage_lun1,Type=fileio

Alias LUN1

#MaxConnections  6

sudo gedit /etc/initiators.allow

iqn.2010-02.net.obxbill:storage.lun1 192.168.27.102

iqn.2010-02.net.obxbill:storage.lun1 192.168.27.106

sudo service iscsitarget start

On windows 2003 servers - download and  install iSCSI initiator for Windows 2003

Then Open the iSCSi Initiator and use the Discover tab, type in the IP of your Ubuntu target, click Logon button

When you see the disk in disk mgr, initialize format select extended partition, then choose ntfs as usual.

Tomorrow, I'll put the process together for building a 2 node cluster.  From there, you can repeat the above process in order to present additional luns to your cluster for things like building a SQL cluster.

See the number of SQL connections to a database

SELECT db_name(dbid) as DatabaseName, count(dbid) as NoOfConnections,
loginame as LoginName
FROM sys.sysprocesses
WHERE dbid > 0
GROUP BY dbid, loginame

Change the location of the TEMPDB

Use the ALTER DATABASE statement, specifying the logical file name as follows:

use master
go
Alter database tempdb modify file (name = tempdev, filename = 'E:\Sqldata\tempdb.mdf')
go
Alter database tempdb modify file (name = templog, filename = 'E:\Sqldata\templog.ldf')
go

You should receive the following messages that confirm the change:
Message 1
File 'tempdev' modified in sysaltfiles. Delete old file after restarting SQL Server.
Message 2
File 'templog' modified in sysaltfiles. Delete old file after restarting SQL Server.
Using sp_helpfile in tempdb will not confirm these changes until you restart SQL Server.
Stop and then restart SQL Server

MOSS Search Service problem - crawl failing - bad credentials

The resolution for this was to add the following registry key

1) Click Start, click Run, type regedit, and then click OK.
2) In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3) Right-click Lsa, point to New, and then click DWORD Value.
4) Type DisableLoopbackCheck, and then press ENTER.
5) Right-click DisableLoopbackCheck, and then click Modify.
6) In the Value data box, type 1, and then click OK.
7) Quit Registry Editor, and then restart your computer.

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

~Sandeep Lad

Then -

- stopped the "Office SharePoint Server Search" service from Central Administration
- restarted the "Office SharePoint Server Search" service from Computer Management > Services and Applications > Services
- started the "Office SharePoint Server Search" service in Central Administration
- reconfigured the search settings
- did a full index AND an incremental search.  The full index did not give me complete results, so I had to run the incremental.

Freelance - eLance!

http://www.elance.com

Just in case... :)

Removing suhosin from Ubuntu

http://www.ambitonline.com/nextrelease/archives/113-How-to-Ubuntu-PHP-Remove-Suhosin.html

and

http://ubuntuforums.org/archive/index.php/t-698306.html

I was looking at reasons to do this since apparently it's for protecting your mySQL and other sloppy php code, etc.

Then I found this little article listed above. Hope it helps

Ubuntu - Apache2 - cURL?

Recently, I installed a plugin where one of the features wouldnt work because it said that something called cURL wasn't installed on my server.

Hmmm...

If you use PHP, you may need to use cURL, which is one of the most popular extension. PHP CURL functions are available through the use of libcurl, a library created by Daniel Stenberg, and allow you to connect and communicate with web servers using many
different types of protocols.

Assume you have already setup LAMP. To install or setup cURL on your Linux machine like Ubuntu, run the following line of shell command in your terminal:

sudo apt-get install curl libcurl3 libcurl3-dev php5-curl

Now you have PHP cURL installed, the next thing you need to do is to restart apache2, run the following command in your terminal:

sudo /etc/init.d/apache2 restart

how to test email via telnet

telnet xxx.xxx.xxx.xxx 25
HELO
MAIL FROM:you@hostname.com
RCPT TO:them@someplace_else.com
DATA Tells you to send data then CRLF period CRLF at end
You type your message then CRLF period CRLF (ie, type a period on a line by itself then hit ENTER) 250
QUIT Signoff message

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 :)

Hearty Coconut Curry Butternut Squash Soup

Ingredients
1 butternut squash, halved and seeded
2 large onions, peeled and quartered
1 medium head garlic
6 cups vegetable broth
1 bay leaf
1 teaspoon brown sugar
1 teaspoon yellow curry powder
Optional spices - Tumeric, cumin and corriander (maybe a teaspoon of each to taste)
1/2 teaspoon dried oregano
1/2 teaspoon ground cinnamon
1/4 teaspoon ground nutmeg (optional - we aren't a big fan)
Salt and pepper to taste (I like pepper :) )
1 cup plain yogurt
1 can coconut milk
1 package of tofu (16 oz) - drain and cube into bite size pieces
1/4 cup chopped fresh parsley (optional)
Fresh lemon juice for when serving (optional - but it's nice and bright with it :) )

Directions

1. Preheat oven to 350 degrees F (175 degrees C). Line a baking sheet with parchment paper or aluminum foil.


2. Place squash halves and onion onto the prepared baking sheet. Wrap garlic in foil and set with other vegetables.


3. Roast in the center of the oven for 45 to 60 minutes, until the squash is tender. Remove from oven and set aside until cool enough to handle.


4. Squeeze garlic cloves out of their skin like paste into a food processor. Scrape the flesh from the squash and place into the food processor along with the roasted onion. Save about a third of the squash meat and chop into cubes or chunks to stir in last. Puree until smooth. Add vegetable broth if necessary.


5. Transfer the pureed mixture to a stockpot and stir in vegetable broth. Season with the bay leaf, brown sugar, curry powder, other optional spices, oregano, cinnamon, nutmeg and salt and pepper to taste.


6. Add tofu and remainder of squash meat and then, bring to a boil and simmer gently for 10 minutes.


7. Remove bay leaf and serve hot. Garnish with a dolup of yogurt and fresh parsley if desired.

Pie Registration and strange php error

in order to fix the error - edit the php.ini
set the following
short_open_tag = On

Don't forget to restart your web services. (IIS, Apache, whatever...)

How to auto delete files older than 5 days

Here's how to auto delete files older than 5 days. Open Notepad, enter the following:

Forfiles -p C:\backup -s -m *.* -d -5 -c "cmd /c del @path"

Save as something like: RecycleBinCleaner.cmd

Then create a service account in AD or a local user account with admin rights on the local IIS box and setup a Windows  Schuduled task to run it every night using that account.

 Bedeep, bedeep, bedeep... that's all folks! :)