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