Switching from Android to Windows Phone 7 Part 1: A leap of faith


Now that I have been entrenched in software upgrades and project phases throughout the week, I decided to take a side trip for some light weekend insight.
I have been a loyal, maybe sometimes diehard, Android user. I have the Original Galaxy S from AT&T along with an Asus Transformer TF101. I’ve spend endless hours customizing, downloading app after app and striving for some form of Fung Shui design that will never attain perfection.
As of late my problems with the platform itself have started to mount. The ever increasing time spent installing and uninstalling, playing games, cleaning it up just to make it messy again. I can honestly say for a phone I was plain bored with it. I cannot say the same for my tablet, but why? It’s simple, I am using it every waking minute of the day. Not looking at it for some mundane status update from the droves of social networks it connects too.
During the lifespan of my Android phone I had used the Blackberry phones for work and developed a health disdain for a dying brand. The phones themselves are light years behind in design and fail to keep up with the software technology of tomorrow. Eventually they will either die or as it seems strike a deal with Microsoft and be assimilated into the Windows Phone. This in itself would cement Microsoft’s place in the corporate environment for security standards.
So why switch?
Aside for some of the reasons I mentioned earlier, there were a couple of nagging issues that kept me continually annoyed with my phone.
1. Every time I plug in the phone to charge it has to force close some form of tethering app that I have never used nor do I pay for on my cellular plan. Often times it would just go black and force a battery pull to recover.
2. Updates. Hmm, where do I start? Well first, the Galaxy S won’t be getting Ice Cream Sandwich. Second, when updates do manage to come around there is no set timeline to when they will get deployed.
Part of my displeasure of late even looking at new phones is the lack of standardization amongsths manufacturers and carriers. Everyone has a different flavor. While at first this was delightful, after awhile it just becomes cumbersome. Different update schedules for each, different launchers, different pre loaded apps you can’t remove, etc etc. It seems these phones are starting to suffer from bloatware as is so common in household computers. Not to mention the increasing virus landscape that is cropping up.
During this time we had ditched our Blackberry’s at work and plunged head first into the Windows Phone 7 platform. The integration with Microsoft Office 2010 and Exchange 2010 made it a perfect choice to start with. Once disgruntled Blackberry users were overjoyed at a phone that was easy to use and light years ahead of Blackberry.
Using one of these phones was a delight, I was able to see the transition from the 7.0 to 7.5 software and the notable advances that were being made. I found myself using my android less for phone-like activities and more for just catching up on my “Draw Something” games.
When I finally decided to take a really close look at the phone I was able to get down to the meat and potatoes. What would I have to trade off, and what would I gain?
Social Integration:
  • Google+ along with many Google apps (Maps, Voice, etc) would go missing.
  • Google+ has been confirmed in the next update along with more Google integration.
  • Facebook has a much smoother app on Windows than any other platform.
  • Almost all the major social networks are already integrated into Windows Phone.
Customization
  • (Sarcasm on) Oh noes, i won’t spend hours customizing my phone? That’s why I have a tablet.
  • While customization is not as granular on Windows Phone, it is available to an extent without compromising the standardization of the sleek Metro UI.
  • Major bonus: All carriers/manufacturers will look the same thanks to Microsoft’s strict design guidelines.
Apps
  • While Apple and Android still have the largest app markets there is a commonality missing in the multitudes of apps to be found.
  • The Windows app market continues to grow while keeping apps within the same design standards of the phone itself. Instead of being just an app on the phone the flow seamlessly into the overall design.
  • Apps are not the same on both markets and since it is a smaller market you will need to find 3rd party replacements if you want a like for like experience.
I ended up finding the best solution to get me out of my Android mindset. Costco. With a special on the Lumia 900 for $49.00 with a $49.00 rebate in new 2 year contracts it was the perfect opportunity to try it  and lets the cards fall where they may. If I found I could not live without my Android induced madness I would be able to return it in 30 days.
The Nokia Lumia 900 I had actually seen at the CES (Consumer Electronics Show) in Las Vegas before it was released for public consumption. It took “Best of Show” in the mobility platforms. I was enamored with it since I first saw it. An innovative design wrapped up with a solid performance package.
It was a “Leap of Faith” literally. I must say so far that faith has been unshaken. This phone has surpassed my expectations in a very short period of time.
In “Part 2” I will highlight some of the likes and dislikes of the platform.
Is anyone else disgruntled with their Androids? Lack of updates?

Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 3


Cleaning up errors after installation of Exchange 2010 in a co-existing environment setup.

At this point the new Exchange 2010 Server is peacefully co-existing with the Exchange 2003 Server. I have not changed routing or anything.

Referring back to Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 2, I ran into a few errors during my 2 week testing period. These errors appeared every 15 minutes in the event log and were always in the same group of 3.

Event ID: 2501

Source: MSExchange ADAccess

Process MSEXCHANGEADTOPOLOGY (PID=1416). The site monitor API was unable to verify the site name for this Exchange computer – Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.
——————————————————

Event ID: 2604
Source: MSExchange ADAccess

Process MSEXCHANGEADTOPOLOGY (PID=1416). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object EX2010 – Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
——————————————————
Event ID: 2601
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGY (PID=1416). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account – Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
——————————————————

After hours of scouring the web I found the problem revolved around the network bindings on the new Exchange 2010 Server. The server itself had 4 NIC cards with only a single card in use. This caused problems when it was trying to retrieve information from servers.

Solution:
 To modify network adapter bindings in Windows Server 2008
    1. Log on to the computer by using an account that has Administrator rights.
  • Click Start, click Run, type ncpa.cpl, and then click OK.
    1. In the Network Connections dialog box, press ALT+N to display the Advanced menu.
    1. Click Advanced Settings.
    1. In the Connections box, click the active network connection, and then click the arrow to move the connection to the top of the list.
  • Click OK.
    1. Restart the Microsoft Exchange Active Directory Topology service. When you restart this service, the following dependent services must also be stopped and restarted:
    • Microsoft Exchange Transport Log Search
    • Microsoft Exchange Transport Log
    • Microsoft Exchange Service Host
    • Microsoft Exchange Search Indexer
    • Microsoft Exchange Replication Service
    • Microsoft Exchange Mail Submission
  • Microsoft Exchange Mailbox Assistants
    • Microsoft Exchange File Distribution
  • Microsoft Exchange EdgeSync
  • Microsoft Exchange Anti-spam Update
Resources:

Did you find this solution helpful?
What other odd errors have you run across?

Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 2


Now that we have finished installing our Pre-Requisites we can move on to prepping the server for Deployment.

Step 1: Server Configuration

1. After building out our shiny new Windows 2008 Server R2-64bit we are going to assign the roles to the system. Make sure all options listed are check marked!

  • Start > Server Manager > Roles > Add Roles > Next..
  • Web Server (IIS)
  • Security
    • Basic Authentication
    • Windows Authentication
    • Digest Authentication
  • Performance
    • Static Content Compression
    • Dynamic Content Compression
  • Management Tools
    • IIS Management Console
    • IIS 6 Management Compatability
      • IIS 6 Metebase Compatability
      • IIS 6 WMI Compatability
      • IIS 6 Scripting Tools
      • IIS 6 Management Console
  • Next > Install > Finish.
  • Reboot if required.

Next we add Server Features as follows

  • Start > Server Manager > Features > Add Features…
  • .NET Framework 3.5.1 Features
    • .NET Framework 3.5.1
    • WCF Activation
      • HTTP Activation
  • Remote Server Administration Tools (Installed)
    • Role Administration Tools (Installed)
      • AD DS and AD LDA Tools
  • Reboot

2. Now we set the startup type for “Net Tcp Port Sharing”

Start > Run > Type “Services.msc” and hit enter.

 

Find NET.TCP Port Sharing right click and select Properties. Set the Startup type to Automatic and hit Apply. Close the window.

Step 2: Deployment

Now that our server is prepped lets move forward with the installation. Run your install DVD or Setup.exe from the install directory.

First step is to select “Step 3: Choose Exchange language option” and select “Install languages from DVD.”

Once finished select “Step 4: Install Microsoft Exchange”. Wait for the setup to start.

At the Introduction screen hit “Next” and then Accept the License Agreement and hit “Next” again.

Select “No, we don’t want error reporting”.

Installation Type will be “Typical” and checkmark the box at the bottom that says “Automatically install Windows Server roles and features required for Exchange Server”. This will install anything we may have missed.

This option only shows if you are installing Exchange 2010 with SP1 included.

Next you will be asked to Configure Client Access to your external domain. If this will be internet facing, click the Checkbox and enter your external domain name (for example, webmail.yaya.com).

The next step is to configure Mail Flow settings. Click browse and select your Exchange 2003 Server. Click Ok and Next.

Next Exchange will automatically fire off it’s Readiness Checks. Pay close attention to the results on this page. You will need to correct any errors that are found before moving on. If you are using Outlook 2003 in your environment you will need to replicate the Free/Busy folder on the server to every other server in the domain. I didn’t personally need to do this but more information can be found here: http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/

Once the setup is complete click Finish!

On your Exchange 2003 server you will now see a new Administrative group called: FYDIBOHF23SPDLT. This is Microsoft’s geek humor. Rolling all the letters back will reveal Exchange12Rocks lol.)

Now we are ready to enter our product key. Open the Exchange Management Console, select “Server Configuration” > Select your server > Select “Enter Product Key” in the right pane.

Add your product key

This for me was a good stopping point to ensure that everything was running smoothly. Test your email inbound and outbound to ensure mail flow is moving. I like to let the server burn in a few days before moving forward so that I can make sure there are no minor annoyances to deal with.

Problems? I think not! Well maybe…

I ran into a peculiar issue in my event log on the new Exchange server.

Problem: Every 15 minutes the event log would register 3 errors.

Event ID: 2501
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGY (PID=1416). The site monitor API was unable to verify the site name for this Exchange computer – Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.

Event ID: 2604
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGY (PID=1416). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object EX2010 – Error code=8007077f.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

Event ID: 2601
Source: MSExchange ADAccess

Process MSEXCHANGEADTOPOLOGY (PID=1416). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account – Error code=8007077f.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

These errors took awhile to track down. Since my server wasn’t happy then I wasn’t happy. The Exchange Server had four NIC cards but we were only utilizing one of them. The problem was with the Bind placements for the NIC that was active. Here’s how to fix the issue:

To modify network adapter bindings in Windows Server 2008

  1. Log on to the computer by using an account that has Administrator rights.
  2. Click Start, click Run, type ncpa.cpl, and then click OK.
  3. In the Network Connections dialog box, press ALT+N to display the Advanced menu.
  4. Click Advanced Settings.
  5. In the Connections box, click the active network connection, and then click the arrow to move the connection to the top of the list.
  6. Click OK.
  7. Restart the Microsoft Exchange Active Directory Topology service. When you restart this service, the following dependent services must also be stopped and restarted:
    • Microsoft Exchange Transport Log Search
    • Microsoft Exchange Transport Log
    • Microsoft Exchange Service Host
    • Microsoft Exchange Search Indexer
    • Microsoft Exchange Replication Service
    • Microsoft Exchange Mail Submission
    • Microsoft Exchange Mailbox Assistants
    • Microsoft Exchange File Distribution
    • Microsoft Exchange EdgeSync
    • Microsoft Exchange Anti-spam Update

Has anyone else run into odd problems such as these?

What was your install experience like? Did you puke?

Resources:

http://technet.microsoft.com/en-us/library/dd789571(v=exchg.80).aspx
http://www.petenetlive.com/KB/Article/0000234.htm – Best resource I found. Images from here all credit given, very well done!

DevConnections Oct 29- Nov 1, 2012 Bellagio Las Vegas, NV


The Journey Continues:

Join Microsoft and industry experts as they help you navigate new technologies and triumph over the challenges of today’s ever-changing developer market. Connections Conferences brings IT Pros and Developers together with experts and peers to answer questions, strategize, and build relationships that will keep you and your company competitive in today’s market. Attend sessions that are relevant for TODAY – go back to the office with practical tips and tricks that will help improve productivity and drive down costs. The conversation begins here in October. You won’t want to miss it!

Got your tickets?

http://devconnections.com/