Search This Blog

Thursday, March 27, 2014

Converting an Evaluation/Trial SQL Server 2008/2012 Built with VL Media to Full Licensed Version

I built a new 2008 R2 SQL Standard server using Microsoft Volume Licensed media.   The media comes with the product keys built in to the ISO/setup.  I built it on an evaluation/trial because I was still waiting on purchase approval for the core licenses and since Microsoft gives a generous trial period of 180 days I had plenty of time to buy my licenses before the trial would run out.

A couple of months into the trial and I had my licenses ready to deploy.  I came across this tip on a message board:

"Go to Microsoft SQL Server Configuration Tools, navigate to SQL Server installation Center and click the Maintinance link and choose Edition Upgrade"

The problem with this is that if you do this from the server installation instead of from media, you will get an error and it will ask you for the product key.  Your upgrade will fail, leaving you to cancel the upgrade and therefore you will have a partial install.  It seems as if the evaluation license was even deactivated when this happened because I tried to go back and choose evaluation and it would not let me complete the setup.

I thought I may have to do an uninstall/reinstall of SQL but then I decided to try and run the upgrade from the media I used to install it originally.  It gave me the same options as the Edition Upgrade that I originally used except this time it filled out the Product Key field for me.  Excellent.  Upgrade completed in a few minutes.

You can also do this via command line.  Open cmd.exe and launch setup.exe with the following command line:

Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=<MSSQLSERVER or instancename> /PID=<PID key for new edition>" /IACCEPTSQLSERVERLICENSETERMS

Wednesday, March 12, 2014

3 reasons I like Crashplan more than Carbonite

I have been a Carbonite fan for many years.  I've used it at home and at work.  Previously, I used it on home office employees in order to capture backups of their work data.  I've used it to backup my home server and home laptops and desktops.  I'm also currently using Carbonite for Business in order to backup some email archives that exist only on users local machines.  It's extremely reliable and it's saved me a few times through the years.

That being said... I have tried out Crashplan's similar service and I'm loving it.  Here is why:
  1. I LOVE the weekly email reports that I receive from Crashplan.  Particularly for my home server because I don't look at it often.  It lets me know when the backup size has increased/decreased and if it loses connection with Crashplan and can't do a backup.


  2. Crashplan's basic plan ($69 per year) lets me backup my large external USB drives that are plugged into the machine being backed up.  Carbonite makes you subscribe to a more expensive $99 (Carbonite Personal Plus) per year plan to backup your connected external drives.  This makes Crashplan a more economical choice if you need to backup external drives.
  3. Crashplan has the Backup to a Friend feature and it's just awesome.  This is something done in business all of the time, offsite backups to a secondary location.  Even if you can't afford Crashplan Central (any one of their current paid subscriptions), you can use it to backup your data to a friend, neighbor or relative's computer.  If you both have space to support your files and your friends you can essentially swap backup space.  They can backup all of their information to your PC and you can backup all of your information to their PC.  It's all encrypted so your friend/relative/etc cannot actually view and use your data.  If your computer crashes, you can use Crashplan to recover your files and it will move them from your backup on the other machine to your new machine!  Pretty cool given it's free!







Tuesday, January 7, 2014

How to Fix OneNote Opening When Using Remote Desktop

Microsoft's OneNote started opening up on an admin machine when we would use remote desktop to connect to a particular server.  If I closed OneNote while the connection was still active, it would open up again.  

I was connecting to my machines using the mstsc /v:servername /admin to connect to the machines as they are virtual machines and this connects you to the console just as if you'd walked up to a physical computer to login.  

To stop the problems with OneNote do the following:

  • Open up Remote Desktop (mstsc.exe for the command line)
  • Type the name or IP of your server in the box
  • Click 'options' to expand the window

  • Uncheck the printers selection

  • Click connect and login to the server; disconnect
Now when you run mstsc /v:servername /admin it will use the settings you just set.  OneNote shouldn't open up when connecting to RDP after this is complete.






Friday, November 15, 2013

Getting/Activating Microsoft RDP (formally Terminal Services) Licenses on the Quick

I had this come up yesterday and was unable to find a good source of info on it so I'll share my experience and hopefully help out another admin one day.

We have a Microsoft Select Agreement.  From what I can tell you must have this or a Volume License Agreement for this to work for you.

We had a server in one of our Canada locations setup as a TS server and it was running on the 120 trial period while we were obtaining licenses from Dell.  We'd already sent in our order to Dell and we were waiting on the licensing to go through.  Getting these licenses usually can take a week or more.  Because our PO had wrong numbers on it, our order was delayed and we ran into our 120 expiration yesterday, thus no one could get on the server the next day.

I first called Microsoft's ordering line and that was of no help at all.  Then I called tech support, they couldn't help either.  Then Dell emailed me saying I could activate them immediately after I placed my order as long as I was on a select or volume agreement, Microsoft will activate them on the phone!  I had no idea, we were ready to rebuild the server or build a secondary server in it's place.

I called the Microsoft Activation Support line at 888-352-7140 and was connected to an agent.  The agent asked for the License Server ID of the server.  You can get this by going in to RD Licensing Manager and right clicking the server name > properties.  I had to provide him with our company name, the type of licensing (user CAL) and how many licenses as well as the select agreement number.

I tried to activate with phone activation but it kept giving me an error of "The RD Licensing Manager is unable to verify the license server ID.  Ensure the license server ID is entered correctly, and then retry this operation.  Message Nunber 0x13a3""  The guy on the phone couldn't help me further so he told me to call support.

Leave it to Microsoft to give me a stupid error.  You cannot retype the ID, it's generated by the server!

I started to play with settings to see if I could get it working.  To fix this I had to switch the activation from telephone to automatic.  This activated quickly.

I then configured the Remote Desktop Session Host Configuration to use user cals and added the license server.

Just a note, this was somewhat buggy.  The licensing, though configured correctly, did not start working right away.  I first tried to restart the services but that didn't work.  I rebooted the server and it still didn't work until about five minutes after the reboot.  I found another post about someone who let the RDP free period expire without having a license server configured first and it mentioned it being a bit buggy upon reactivation.

http://social.technet.microsoft.com/Forums/en-US/6e90a71e-fea6-4229-a66b-aa7677d1a5a6/rdp-the-remote-session-was-disconnected-because-there-are-no-remote-desktop-license-servers

So... if you're in a crunch and you've already ordered your license, try calling Microsoft.

Thursday, August 29, 2013

Symantec Backup Exec 2012 Sucks; Backup Exec Alternatives


This software has always had it's quirks but I've used it for many years and I've come to like it because I know it pretty well.  Well... that was until I installed BE 2012.

Upon searching the internet for information on this product (you know you hate it when you search for Backup Exec 2012 Sucks) and it's issues I eventually stumbled across this blog post at Symantec.  Witness the numerous IT administrators on the forum who are just completely over dealing with Symantec when it comes to the new version.  They obviously have already lost many, many customers from this crapware.

If you want to feel entertained, read the comments here.

Some comments from the post:

We need support for new product when it hits the shelves. - JStellato

If others can get a product out the door with support and minimal quality control issues within a couple months of GA then Symantec’s current approach seems a little sad.- Tallwood6

Symantec have clearly missed the boat with 2012 yet are now promising limited support, as long as we keep a 2008 server spare to load their product on. How can I propose this to an end customer? - IMW

So in August we will have a six month window for when BE will be updated, so that probably means minimally we are looking at February of 2014. I totally get the quality over quantity argument, of course we all want the software to work and work well. But when we can look at other vendors who are releasing updates on time and of high quality, it is hard to rationalize staying with Backup Exec, no matter how much I like the product. - Clifton Hastings

I agree that 2012 should have been abandoned and 2010 been the way forward. I tried to work with 2012 but it was 3 months of frustration so I rolled back to 2010. Now I am trapped when we rollout 2012 servers, I won't be able to back them up! - Mgamiet

So let me get this straight. This whole time you have been in Beta and claim to be working on a solution to Backup our 2012 servers and then it is released and CANNOT be installedo n Server 2012. What good is the software if I can't install it? I can install a remote agent, but where do I install the actual Backup Exec Server? - GeorgeSVA


First major issue:  YOU CANNOT INSTALL BACKUP EXEC 2012 ON SERVER 2012!  WTF?

Second major issue:  Do not upgrade from BE 2010 to 2012; you will regret it.

You cannot upgrade from BE 2010 > 2012 if you have the DLO (Desktop/Laptop Option) installed.  Even if you remove it, it's buggy to upgrade.  DLO is now a separate product.  We ended up installing BE 2012 on an entirely new server after getting frustrated with the upgrade.



Third major issue:  (I could probably count to a hundred here) The first thing you will notice is that the interface looks updated.  At first sight I was kind of excited that they updated it to look fresh and new.   Then I used it.  It sucks.  But it looks updated.  :)

This version is drastically different from the previous versions.  It's non-intuitive, confusing mess of an interface is a nightmare.  This version does not backup multiple servers in one job.  I understand they approached this from a positive point of "No longer will your jobs fail because of a single resource/server!"  Sounds awesome, right?  Wrong!  Each server has it's own job.

Now with each server having it's own job, Administrators will get spammed with messages for every server, not just a few backup jobs for entire datacenter.

Fourth major issue:  If you have an environment with only one tape drive, not a library, good luck.  The system doesn't want to write multiple server (jobs) to the same tape.  This means if you, like our Canada location, have a single LTO5 tape drive and several jobs, you have to put a tape in for each job.  Even setting the append time low does not fix this issue.  I have less than 1TB of data to write for all servers and yet it wants one tape per server so instead of writing to 1 of these $40 tapes I have to write to four of them.  Since I work in Aerospace, I must keep my monthly backups to tape indefinitely. You can see how this would cost much more over time, specifically when I have much larger environments where we use BE.

It's difficult to see what is going on with a job.  Is it frozen?  Is it waiting for media?  I don't know.  It doesn't prompt for media anymore.  Even when you open a job that is just sitting it's not super in your face about what is happening.

Apparently they just released BE 2012 SP2 and guess what?  After nearly 1.5 years of this product being available they can now backup 2012 servers!  Yay!  Should we get excited that it took them almost 2 years for us to even be able to install a remote agent so we could back up 2012?  I'm not sure what the people at Symantec are doing but they need to get their heads out of their asses and release their updates faster, hire more developers, better project managers, something.  All their competitors have been installing on and backing up systems on 2012 for over a year.

That being said... I went looking for alternatives.  I had a hard time finding tape writing alternatives and so after some research I made a list.

For those of you that use VMWare or Hyper-V... I was giddy when I found out that Veeam 7 now supports tape libraries, tape drives, etc.  Yay for Veeam!  vRanger is another tape writing, virtual backup alternative.  vRanger will also backup physical servers as well whereas Veeam will only do file copy jobs from your physical machines.  Still better than dealing with all of Backup Exec's errors and inability to backup your servers.

For those just dealing with physical servers I will list the alternatives I found here.  I make no claim as to the quality of the product (Yosemite and ArcServ are my favs) only that you should check these out if you want to ditch Symantec Backup Exec.  Many of these will rival them in features, some are more simple; choose based on your requirements.

Backup Exec Alternatives

As for me... I'm going to use Veeam 7 for the majority of my servers.  I have an old BE license that I will use on my few dwindling physical servers until my maintenance runs out next year.  Then I will look at replacing BE with a cheap tape solution.  I may even back them up with Windows Backup and then use the Veeam 7 option of backing up files from physical servers to push them to tape.  Ultimately we will be saying goodbye to Symatec Backup Exec in all of our locations in the US, Canada and Mexico.  Buh-Bye!

Thursday, August 22, 2013

Surface Pro Windows 8 limited connection on wifi & Checkpoint VPN

I have a Microsoft Surface Pro and I finally got around to loading all my essential applications on it.  I'd previously connected to my home wifi without a problem and even one at work.  I loaded up all my important installers onto a usb drive and installed several applications.  I packed up the Surface Pro for my trip to Toronto.  Last minute, I grabbed my usb wired network adapter (untested on my Surface).  I arrive at my hotel in Toronto and I can't get the wifi adapter to fully connect to the hotel wireless.  It would connect with a 'limited connectivity' warning.  My iPhone and iPad both connected without incident. 

I tried disabling, re-enabling the adapter, removing the device and reinstalling it, replacing the drivers, clearing out the profiles on the wifi adapter. 

I took it to our office in Toronto and tried to connect it.  Same problem, limited connectivity.  Plugged in my usb wired connection and it installs the driver.  When I went to "Change My Adapter Settings" in the Network and Sharing Center.  No adapter appeared for the wired connection.

I played with the settings on and off all day.  I tried several other people's solutions that I found listed online.  Then I found a post about someone having a problem with McAfee causing a similar issue.  I remember I'd installed Checkpoint VPN software and Webroot just before I left.  Webroot has never caused any problems like this on the hundreds of PCs we run it on, including a few Windows 8 clients.  When I thought about it, I realized that we have never likely installed Checkpoint on Windows 8 at work. 

I uninstalled Checkpoint VPN and rebooted and voila, my computer joined the hotel wifi.

Here I was upset all day long that I had a bad Surface Pro.  I really did not want to have to exchange this and start over loading apps.  Phew.

Dell M4400 Nvida causes crash when loading and updating Windows 7 x64

I have a Dell M4400 that I use at home for design work.  I decided to give it a boost by upgrading the hard drive to solid state.  The system already has 8gb of ram so it's plenty fast for what I use it for, minus that slow older hard drive.

I decided to load Windows 7 Ultimate x64 on the laptop.  Installed just fine, no issues.  Then I ran the first of the 120+ updates for Windows and the machine started blue screening constantly.  It was hard to even login, at times it would crash on login.  I was worried I may have to wipe it again.

I downloaded updated drivers for the video card and put them on a USB stick. After several attempts to login I was lucky to get a few moments to update the drivers and low and behold... no more blue screens.

So if you're loading your M4400 with Windows 7, I recommend downloading and updating the drivers before running all of the Windows updates.