Migrating from Wordpress to Google Blogger

Piece of cake... or Pie... whatever you like I guess

• Open a browser tab:
• Login to your Wordpress site > 
• Tools > Export > All Content > Click Download Export File
• Mine was called something silly like:


• bill039scrappytechblog.wordpress.2012-07-17 Convert your backup!
• Then waltz over to this conversion page...
• http://wordpress2blogger.appspot.com
• browse > find your file > click ok, then Convert  I think
• saves as something boring like blogger-export.xml... yay!
• NOW! --->

• On another browser tab, go to Blogger.com:
• Register or Login with your email address (doesn't matter if it's not an @gmail.com).
• Create a blog > select Settings, then select Import, or something like that
• Then browse for your converted file... blogger-export.xml
• click ok... I think.
•  

If I feel bored, I might stick some screenshots up here, but, I'm tired and don't feel like it right now. So, good night.   :]

Coming back soon!

Hi there everyone,

It's been a while since I've blogged out here. Over the next week or so my plan is the following:

• Backup this wordpress blog content, database, etc.




• Export, site, mysql db, wordpress files




• Create a new blog over at blogger.com with my Google Apps domain


• Import this old blog and all it's crap to the new blog,




• Categorize all of the old posts, meta data, etc




• Explore Google Analytics with the new blogger site


• Stuff a bunch of new posts regarding my home lab configurations




• KVM Host Builds




• VMBuilder scripts for building VMs


• Virtual HD file Conversion scripts




• SSH Tips & Tricks




• Forward Local Tunnels


• Reverse SSH Tunnels




• Google Apps Stuff




• Legacy Systems - Exchange & Domino


• Data Migration


• Setup


• SSO


• Mail Routing


• Spam/AV


• Permissions


• LDAP




• More and more to come to this new laundry list of silliness to write down... :)

SubSonic - FlashPlayer Broken ? ?

Well... forget about banging your head on the wall trying to fix those poor little client machines.  It's not you... It's me...  We've all heard that one before.

But this time, it's true.  Especially when you've hammered down your web-server on a number of occasions, just to see if you could break it...

ok, you ready for the fix?

sudo rm -Rf /var/subsonic/jetty/2169/jsp/org/apache/jsp/WEB_002dINF/jsp

Keep in mind, I'm running mine on a QEMU Virtual Machine that is Ubuntu 11.04 x64 with the most basic of basic installations. No frills people.

I think the cache files got stuck or corrupted at some point during one of my "stress tests"... fun :)

The Google Apps Device Policy App apk file

Chicken and Egg...

There are some of you out there who have tried this know what I'm talking about.

I hope this post helps some people out there.

Any apk or Android app file that doesn't come from the market directly apparently is typically considered a non-market app, even when the app being backed up originated from the market, (i.e. the Google Apps Device Policy app).

Here's a link to the Google Apps Device Policy apk file that you can download right now from my site. The version here is 2.00 from market.android.com



 

 

 

 

 

The app I used to create the apk backup file is called Astro File Manager.

Here's a link to the apk for the Astro File Manager if you need it

Menu > Tools > Application Manager/Backup

Scroll down...

Select Device Policy, tap Backup
- yeah, it's not listed as Google Apps Device Policy. Only listed as Device Policy in the list of apps to backup.

The backup file is now saved to the SD card as an apk file and can be copied to a website or even emailed to users. When its emailed, the user should be able to sign-in to their web based email, even through a 2-factor solution like SecureAuth, on a Google Apps email account.

Then the user can install and configure the device policy apk file after they've allowed non-market apps.  DON'T FORGET THIS PART!!

BTW, u can't do this on AT&T Android devices. They took the ability away... erg!




Settings > Applications >  enable Unknown Sources (allow installation of non-market applications)

Once installed, they should disable Unknown Sources. I would recommend that this be done by either the mobile device team or have the phone provider pre-install the app prior to shipping to the users.

Now your user can configure their primary account on their Android device. This gives them the full functionality of GTalk with that same account.

Otherwise, if the user uses their personal Gmail account as their primary, they will only be able to use GTalk with their Gmail account and not their Google Apps account. GTalk on an Android only functions with one account... the first, or rather their primary account on the device.

The above applies to Android 2.2 devices connected to a Google Apps for Business, Education and Gov't Edition domains configured with 2-factor sign-in using SecureAuth SAML assertion.

Also, for security reasons in this scenario, the users do not have their Active Directory passwords synchronized between AD and their accounts on Google Apps.

So, when a user configures their account with Accounts & Sync, on the screen with the Create and Sign-In buttons, select Menu > Browser Sign-In. This will allow the user to setup their account through the 2-factor Sign-In process.

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'