server2003

#TechTuesday - Windows Server 2003 End of Life

Are you running Windows Server 2003 in your datacenter? Time is running up; less than 45 days until Windows Server 2003 hits its end of life. What does this mean for you and your business? This means that after July 14, 2015, Windows Server 2003 will no longer be getting any security updates or support. This will leave your networks unsafe and at risk to all different kinds of threats and breaches. What will happen if you don’t migrate? Your company is in danger by ignoring the deadline. 


The dangers can include:
• Putting your entire document library and applications at risk
• Increasing your costs for maintenance of servers and aging hardware
• Failing to meet industry compliance
• Increasing your risk of corrupted data
• Possibility of downtime


Don’t waste any more time or resources - migrate over to the latest and greatest Microsoft Server now!

Want to know more about the end of life on Windows Server 2003? Read more at the Microsoft webpage:
https://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/

NetServe365 can help you out with your Windows Server 2003 migration plan. We can flawlessly migrate your server and help ensure continued compliance while retaining data security, company productivity and business efficiency. Need more help other than Migration Assistance? Learn more about what NetServe365 has to offer, check us out at www.netserve365.com

Windows Server 2003 Support Ending

The end of Windows Server 2003 is rapidly approaching. On July 14, 2015, Microsoft will no longer offer support for Windows Server 2003. No support from Microsoft means:

·      No updates
·      No compliance
·      No applications support

If your business is running Windows Server 2003 after the July 14 deadline you will be at an increased risk for:

·      Cyber attacks
·      Unsupported applications
·      High penalties due to lack of PCI and HIPAA compliance
·      Added costs for additional firewalls, security, etc.

Learn more by visiting Microsoft’s website here and read what U.S. Homeland Security has to say.

Some migrations are taking more than 90 days to complete, therefore Microsoft recommends customers running Windows Server 2003 migrate their systems to an up-to-date system such as Windows Server 2012 R2 or Azure as soon as possible.  To find out more about the end of support for Windows Server 2003 and migrating your infrastructure to a new system, call or e-mail your local IT specialists at ProBleu today!

Cloning Windows Server 2003 With Ghost

I try to learn something new every day. Yesterday, I learned a bit about cloning Windows Server 2003 system disks with Ghost.

We run Cisco wireless equipment at work.  We currently use a Dell server to host the Cisco Wireless Controller System (WCS) that helps us configure, monitor and troubleshoot the wireless system.  It’s a glorified website and database that controls and reports on all of the wireless equipment.  We purchased a new server and needed to migrate the data from the old hardware to the new.

The way the WCS creates a backup is by creating a temporary file in a working directory within the WCS installation.  In our case, this was on our system drive.  We ran out of space and needed a larger hard drive to be able to create a current backup and migrate the data off of the legacy system.

We used Ghost to clone the data off of the system drive on to a larger capacity hard drive.  That part was easy.  Set Ghost to clone a partition to a partition.  Select your source (System drive) and destination (new larger capacity drive) and let it go.

2 hours later we came back and logged in, shut the machine down and swapped the drives in order to boot from the larger capacity drive.  The system came right up, but when we attempted to log in, we were immediately logged out and taken back to the ALT-CTL-DEL screen. 

After some research and a little testing, we found that our new cloned drive was being assigned a different drive letter (D) than the original system drive ©.  As a result of both the disks being present when booting into the OS.  We found this by remotely connecting to the server’s file share and noticing that there was no default “C$” system share.  We found the other drives including “D$” which was the drive we cloned the original system disk to.  Odd.

The problem arose when the server finished cloning.  Once Ghost is done cloning data, it reboots.  In our case, it rebooted into Server 2003 and was assigning a drive letter to the drive that held our cloned data.  Instead of “C” it was “D”.  As such, the system booted (somehow), but anything referring to C:\ was broken. This included the login sequence critical file USERINIT.EXE which is located in C:\windows\*somewhere*. \

So we had to clone and catch it before it booted into windows.
EDIT: It turned out that we needed to not log in once the system comes back up after the reboot.  It was when we logged in that the drives were assigned letters.