Tag Archives: Microsoft

Windows Server 2016 Administration: Modifications

Posted on by

Windows Server logoContinuing with a previous post on the upcoming Windows Server 2016, we look at administrative improvements in 2016. There are many articles about Windows Server 2016 that tell us about the new features we should expect, but this blog is about the modifications we should expect. We are talking about changes made to the features we already utilize in the Windows operating system. There are many changes coming and this article is not going to cover every one. It will focus on the significant changes that will affect a Windows Administrator’s day-to-day usage of the operating system, our most common tasks.

  • The Interface – The GUI will be similar to the GUI in Windows 10. The ‘Start’ button is back. That should make a lot of administrators happy being that the lack of a Start Menu was one of the top complaints with Windows Server 2012. However, we will also see a change in how we find the items we utilize. Navigation of menus and features will have some differences. For instance, certain settings may not be where you expect to find them in relation to Server 2012 and 2008.
  • Active Directory – Windows 2003 functional levels will be deprecated in this release. If your Active Directory is still at a Windows 2003 functional level or you are still utilizing File Replication Services, it is time to enact a plan to upgrade the domains functional level and move on from FRS. Enhanced security features and certificate services will improve compliance.
  • PowerShell – Everything we do in the Windows 2016 GUI can be done in PowerShell because everything done in the GUI is controlled through PowerShell. However, the reverse is not true. There are tasks you will need PowerShell commands to accomplish because there is no GUI for the task. PowerShell 5.0 will be expanding the language, commands, and feature-set to support the modified and new features in Server 2016. This article is focusing on the administration side, but we have to note that there will be many modifications/changes on the developer side as well like using classes to develop.
  • Windows PowerShell Console – For years now, we have been working with PowerShell, but our primary console to perform the work within is rudimentary. Many of the features people have been looking for in a language editor are being incorporated into the updated PowerShell Console. Features like drag-and-drop, cut-and-paste, and more.
  • Storage – While there are new features for file servers and storage clusters, the most significant update to an existing feature affects data deduplication. Optimizations in the handling of large files and large volumes will give improved access and control. Clusters will be able to run in a mixed Server 2012 and Server 2016 mode. Sever manager will be able to control deduplication of backup workloads.
  • Hyper-V – One of the big issues with Hyper-V is that it is not as feature rich as its competitors. Windows Server 2016 hopes to close that gap. Features for handling server upgrades, modifying resources to VMs while active, device access, and more were integrated to close the feature gap. The 2016 Hyper-V Manager is backward compatible so you can manage 2012, 2008, and Windows 8 VMs. Hyper-V Manager no longer has to use the security of the account logged in. You can now access Hyper-V with an account other than the one you are logged in as. Improvements in the handling of server hardware resources give virtual machines improved performance. Even the upgrade process for a Hyper-V cluster has been improved.
  • Remote Desktop Services – The most significant modifications to RDS are the updated clients and browser support. For instance, Edge is fully supported and there will be new Windows 10 and Mac apps available. Device support has been enhanced to include Pen devices. Support for OpenGL applications is also included. New features will enhance the offerings we will be able to give our users like Personal Session desktops.

These are some of the major modifications in 2016 that will affect an administrator. There will be many modifications in Windows 2016. More than what can be discussed here. Hopefully the few changes listed above will prompt administrators to take a look at what is coming and how it could affect their environment. While discussing the modifications to administration from 2016, it is hard not to mention new features. There are many new features are going to affect your role as an administrator. To see more of what is new and changing in Windows Server 2016, check out the Microsoft blogs. 

Feel free to post any questions or comments below or reach me directly by email.

 

AZS-3

 

Craig R. Kalty (CCIA, CCEE, CCA, MCITP:EA, MCITP:SA, VCP)| Sr. Network Consultant craig.kalty@customsystems.com

 

 

©2016 Custom Systems Corporation

Are Cloud Offerings Good for SMB?

Posted on by

The title for this blog came about from a number of our SMB clients asking two questions:

  1. What exactly are cloud services?

  2. Should we be looking into them?

Here is a general answer to the first question: Cloud services are on demand solutions made available to users through an Internet connection from a Cloud provider.  For instance, Office 365 provides an e-mail solution (and more) from Microsoft that users can access anywhere they have Internet access from almost any device.  I can even get to Office 365 from a certain gaming console.  In the early days of cloud computing, cloud referred to services that came through the Internet from a third-party.  However, today we have private in-house clouds as well.

As for the second question; yes, you should be looking into Cloud solutions.  Every year, IT has a buzz-word that rises to the top of the list.  In the ancient past of a few years ago, ‘client/server computing’ was the major buzz-word.  More recently, ‘virtualization’.  Though virtualization is still a major buzz-word today, ‘Cloud Computing’ is now on the top of the list.  There is a reason these buzz-words rise to the top of the list, they are a rising, viable trend for IT solutions.  Cloud may not be for everyone, but there is not a single administrator who should not be looking to see how cloud services can help their organization.  Funny, I said the same thing about virtualization not too long ago.

So, why should your organization we be looking at cloud services?  Here are some major reasons:

  • Lower IT costs without the risk. If you host a service in house, you need the hardware resources to house it, the expertise to build and maintain it, and the resources to operate it.  Most of the time, cloud services are a subscription based service.  When first looked at, the monthly cost of those subscriptions may be substantial.  However, you have to compare it to what it would cost you to have the services in-house.  Add up the cost of the server, the environment to protect the server (power and air conditioning), installation, maintenance, backup, and upgrades.  You get all of that from the cloud without you having to deal or worry about it.  The cloud service has the security and the disaster recovery resources already which means lower risk to you.
  • New methods of collaboration. Sharing ideas, files, and data can be done almost anywhere, anytime, and on any client.
  • As stated above, being able to do things almost anywhere, on any client, at any time.

Most SMB do not have a large IT staff with a wide variety of technology skill sets.  They usually have the one or two people who have to be a jack-of-all-trades.  I have seen places where this person is the head of accounting.  They have a CPA, not a BS in Information Technology.  With cloud solutions, the need for in-house expertise on a product is practically eliminated.  The burden on the ‘IT’ people is lifted and day-to-day IT tasks are reduced.

Here are few examples of cloud offerings and what they give you (some items depend on the subscription level):

  • Office 365 gives you hosted Exchange e-mail services, the latest version of MS Office for multiple devices, shared information and files, hosted storage, and more.
  • Trend Micro Worry Free Business give you cloud administered antivirus. The AV client still resides on each device, but the administration is in the cloud.  This way, you do not need to install AV administration services on a local server.  You can also get to the console from anywhere to perform tasks.
  • Carbonite offers highly compliant backup solutions to the cloud. You don’t need the storage or administration hosted in-house.
  • Microsoft Azure and Amazon Web Services make it possible to put any server, even your entire server infrastructure in the cloud.

There are many more cloud offerings than these.  It is most definitely worth looking at cloud services whether you are a small or large company.

Do you have any questions about the cloud and your business? Custom Systems can help! Feel free to post any questions or comments below or reach me directly by email.

 

AZS-3

 

 

Craig R. Kalty (CCIA, CCEE, CCA, MCITP:EA, MCITP:SA, VCP)| Sr. Network Consultant craig.kalty@customsystems.com

 

 

©2015 Custom Systems Corporation

Windows Server 2003 Migration: Tasks Part 3 – Build and Test

Posted on by

windows server 2003 R2In Part 2, we created a plan that maps out the migration from Windows Server 2003. Now we are at the point where we need to build what we designed. Notice how in all the blogs concerning decommissioning 2003 that I use the words ‘migrate’ and ‘migration’ and not upgrade? I probably should have discussed this sooner, but there is no upgrade. You cannot upgrade 32-bit Windows 2003 to 64-bit 2008 R2 or 2012 R2. No matter your plan and budget, you will need to perform a fresh install on at least one server to start the process. Also, it would be wisest to go to 2012 R2 for many reasons (particularly not having to repeat this process when 2008 reaches end-of-life). For some migration paths, you may need to install at least one 2008 server to go from 2003 to 2008 and then to 2012.

The best place to start would be a test/development environment. We know from experience that there are many smaller shops out there that do not have the budget to create a development environment. Most of them are going to rely on the expertise of their staff or outside services to get their environment from where it is now directly to an updated infrastructure without performing a lot of tests. For those environments, remember to at least do extensive planning and research beforehand to mitigate issues. For those that can build a development environment, the best way to do it is virtualization (there I go again using that word). Remember that you can make a virtual server host out of various hardware platforms. You can even install a robust hypervisor for free. To give you an example, my laptop has an extra drive that I swap instead of the DVD drive. I then manually boot to the extra hard drive where I have XenServer hosting over a dozen VMs. Is it powerful? Not really, but I can run my demo environment from it. The point is we don’t need to break the budget to make a development environment. We may not even need to touch any of the budget. If you did budget for a new virtual environment or to extend an existing one, here is where you can start utilizing that new investment. P2V (physical to Virtual) machine images of your existing infrastructure servers. From there, you can fire up a new virtual machines (VMs) housing 2012 R2 and/or 2008 R2. Once you have the test environment, take snapshots of all the VMs before making any changes. Now you can begin the process of converting your virtual infrastructure in a development environment. If you run into issues, you can utilize the snapshots to reset the environment and try again. Take detailed notes of all the steps and pay attention to any potential problems. Once you have a clear plan with detailed notes, you are less likely to run into the unexpected when updating your production environment.

So, what exactly are we testing in our development environment? There are basic services that almost every shop is going to be utilizing. Active Directory, DNS, and DHCP are the three most common services we will need to migrate to another server. The good news is that detailed directions from Microsoft and other experts can easily be found on the web. Some organizations are going to have the basics and some are going to have more services in use. For instance, some organizations may utilize Terminal Services. Migrating that to Remote Desktop Services (RDS) will be a project in itself (though a worthwhile one).

Here is an example list of services you may/will need to test:

  • Basic services:
    • Active Directory (AD)
    • Group Policy
    • Domain Naming Systems (DNS)
    • Dynamic Host Configuration Protocol (DHCP)
  • Extended services:
    • Certificate Services and Public Key Infrastructure (PKI)
    • Terminal Services
    • Distributed File Services (DFS)
    • Internet Information Services (IIS)
    • Network Load Balancing (NLB)

Each organization is different, so they may have some or all of the items from the above list. A lot of organizations will have more to add to the list. Aside from these services that come in a Windows server, we will need to test hosted applications. This set of blogs has been pretty much focused on the Active directory side of the migration, but what about applications? If you have Exchange, SQL, or another enterprise application hosted on a 2003 server, you are going to need a separate project just to migrate those applications. This may be the opportunity to move from in-house mail services to a cloud-hosted solution like Office 365. It is possible to focus on upgrading our Active Directory infrastructure first and saving the applications hosted on 2003 servers for a later project. However, research the applications to make sure they will still function in an updated AD infrastructure. If not, that is one of those symmetrical projects you will need to have in your plan.

The next step will be implementation into production. At this point, we are ready. We have performed tests in our development environment, gained experience in the tasks, created detailed instruction sets, and realized modifications needed in our plan.

As always, I welcome your comments or questions. Please feel free to leave them below or email me directly. Also, be sure to bookmark our site for more information from Microsoft. Also, please be sure to register for our live, Microsoft event – Windows Server 2003:  Security Risk and Remediation on February 18.

AZS-3

 

 

Craig R. Kalty (CCIA, CCEE, CCA, MCITP:EA, MCITP:SA, VCP)|
Sr. Network Consultant
craig.kalty@customsystems.com

 

 

 

©2015 Custom Systems Corporation

Microsoft Hyper-V vs. Citrix Xen Server

Posted on by

For a few years now, here at Custom Systems we’ve had an ongoing debate between two different Virtualization camps: Microsoft Hyper-V Server and Citrix Xen Server.  Today I am going to take a look at the advantages and disadvantages of each.

Hyper-VIf you’ve read my blog posts before, you can probably guess which camp I’m in.  I’ve been a big fan of using Microsoft Hyper-V as a Virtualization host for a few years, and here’s why:  For starters, the host server is a true Windows Server environment, (excluding Core version).  I’m used to using Windows Servers, and I am very familiar with them.  I know how to install hardware drivers, software updates, etc.  I can install my Backup Software on the host, and make changes to my Virtual Servers from the Hyper-V host console.  When setup properly, I can have a new Virtual Server up and running in a few minutes.

Citrix Xen ServerCitrix Xen Server, by that comparison, is not as easy to manage.  Granted the install process is MUCH faster, but to properly manage your Xen’s Virtual Servers, you need to install the Xen Center Console on a Windows PC or server.  In some environments, that isn’t practical.

Now for the advantages of Xen Server:  There is almost no overhead.  The Xen Server Host can fit on a small RAID 1 partition, needs very little RAM, and doesn’t need to be managed as often as a Windows Host Server.  This allows you to dedicate all of those fast hard drives and RAM to your Virtual Servers, instead getting taken up by a Windows Host Server.  Plus if you use Xen Server as your host server, that’s one less Microsoft Server license you will need.  You can save that license for one of your VM’s.  Also, exporting or migrating a VM with Xen Server is easy and painless.  I wish I could say the same about Microsoft Hyper-V.  (Maybe in the next release?)

Just a few “Gotcha’s”

I have run into a few situations where a third party vendor would not support using their software or hardware on a Xen Server.  At the beginning of the sales process, we will meet with you to discuss your needs and to determine which Virtualization solution is right for you!

AZS-4Chase Reitter
Network Consultant
Chase.Reitter@CustomSystemsCorp.com

 

 

 

© Copyright 2014 Custom Systems Corporation

The End is Near! (for Windows XP)

Posted on by

How many cell phones that were available for purchase in October, 2001 are still in use today? When we see someone on a flip phone, what do we think (or even say to them)? The excitement for new smart phones is conveyed in TV commercials while the lines of people waiting to be the first to have one, is reported on the news. We love our new cell phones and hate using old ones. The technology available today compared to 12 ½ years ago is mind blowing!

But when it comes to our Windows — we love our 12.5 year old systems! Windows XP was officially released by Microsoft on October 25, 2001. While we like using XP and have a comfort level when we sit down at our computer, time marches on. On April 8, 2014 Windows XP and Office 2003 will be officially designated as “end of life.” What does this mean? Starting April 8, 2014, Microsoft will no longer provide security updates, upgrades, or other patches for the operating system or the office products. Below are the details from Microsoft’s website regarding the impact of Windows XP End of Life on your business:

What does end of support mean to customers? It means you should take action now!

After April 8, 2014, there will be no new security updates, non-security hotfixes, free or paid assisted support options or online technical content updates.

Running Windows XP SP3 and Office 2003 in your environment after their end of support date may expose your company to potential risks, such as:

  • Security & Compliance Risks: Unsupported and unpatched environments are vulnerable to security risks. This may result in an officially recognized control failure by an internal or external audit body, leading to suspension of certifications, and/or public notification of the organization’s inability to maintain its systems and customer information.
  • Lack of Independent Software Vendor (ISV) & Hardware Manufacturers support: A recent industry report from Gartner Research suggests “many independent software vendors (ISVs) are unlikely to support new versions of applications on Windows XP in 2011; in 2012, it will become common.” And it may stifle access to hardware innovation: Gartner Research further notes that in 2012, most PC hardware manufacturers will stop supporting Windows XP on the majority of their new PC models.

If you still have Windows XP or Office 2003 in your business environment, you’ll need to start planning a transition to newer operating systems and office products. You’ll likely also need to consider hardware upgrades, as most modern operating systems will not run on older systems designed for Windows XP.

There are many options for upgrades these days. For the operating system upgrades you can move to Windows 7 or Windows 8.1. For Office, you’ll want to upgrade to Office 365. Office 365 is a new paradigm for Microsoft: you can use the software on five different devices per user; you can use it installed on a local desktop or via a web browser; hardware requirements can be reduced with hosted Exchange and hosted SharePoint. The new office product offering is a good move and competes more directly with Google Apps. You can learn more about the new Office 365 by clicking here.

If you need assistance getting your systems upgraded or determining which version of Microsoft Windows or Office is right for you, contact us today!

For more information on Windows XP migration, take a look at our other blogs:

 

DaveDavid Bubb
Sales Director
Network Services Group
David.Bubb@CustomSystemsCorp.com

 

 

© Copyright 2014 Custom Systems Corporation

Cloud-Based Apps vs Local Servers

Posted on by

I get a lot of questions about Cloud computing.  So today we are going to discuss a few of the differences between keeping your applications and files on local servers vs. moving to the Cloud.  We will cover some of the advantages and disadvantages of both, as well as examine my own bias.  We may even discover that I’m (GASP) wrong.  Sound like fun?  Ready?  Here we go!

What is Cloud?

Well, it’s not in the Stratosphere (though THAT would be especially cool!).  Cloud computing usually refers to a service that you pay to store data for you.  Everything from email, databases and files to accounting software can be Cloud based.  Advantage?  No servers to manage or  maintain.  No backups to check, no tapes to change.  Just sign the check on time, and it’s all taken care of for you.

This ain’t your Dad’s Cadillac, er, Cloud.

Cloud computing has been around since the dawn of the interwebs.  Why it’s just becoming a buzzword now is beyond me, but there it is.  Chances are, your bank hasn’t stored your account information in their local branch office in over a decade.  Instead, they pay a hosted service to provide the disk space and backups they need.  Banks used to dial into the data center at a specific interval each day, update any changes and check for problems.  It was painstakingly slow, but it kept your information safe.  Fast forward to today:  Even your grandmother is uploading pictures to Facebook or to DropBox.  Both are cloud.

So is Cloud better?

Well, it depends.  Internet services keep getting faster and more reliable.  So does server hardware.  Having servers in my office means that I get to manage them.  If there is ever a problem, it’s a short walk down the hallway, and I can troubleshoot in a matter of minutes.  Hardware can easily be replaced or upgraded as needed.  Servers have lights that blink, fans that whir, and hard drives that hum in perfect harmony.   And should one of them get out of tune, I can fix it.  If my data is in the Cloud, I have to rely on someone else to keep an eye on their servers.

In some scenarios, I suggest a hybrid of both on-site servers and a Cloud-based solution.  For a medium-size business, this is often the best of both worlds.  For example, keep your data on an in-house file server so you have local, secure access to your information; but use a hosted solution for email.  Email servers take a lot of work and are difficult to manage.  While I’m more than happy to take care of your email server, using a hosted email option may be the most cost-effective for your organization.

Give us a call today, and we can help find the best solution for your business!

Full disclosure:  Custom Systems uses Office365 to host our email and file services.  This article was written on my laptop, but then stored on a hosted SharePoint server for the editor to review and fix my spelling and grammar.

ChaseChase Reitter
Network Consultant
Custom Systems Corporation
Chase.Reitter@CustomSystemsCorp.com

 

 

© Copyright 2014 Custom Systems Corporation

The 10 Commandments of Hyper-V

Posted on by

1. Thou shalt NOT use a dynamic disk with ANY database.  This includes, but is not limited to:  Active Directory, SQL Server and Microsoft Exchange.

2. Thou shalt always provide at least 4G of RAM minimum for the host operating system, and always provide the host operating system with its own NIC and disk partition.  Hyper-V is a jealous host, and will not share with any VM.

3. Thou shalt NOT join the host OS to the domain. Join it to a Workgroup by the same name.

4. Thou shalt always disable time synchronization and disable Automatic Updates on your host server.

5. Thou shalt always set the Hyper-V host to properly shutdown/restart the guest VM’s.

6. Thou shalt NOT use pass-through disks nor use SCSI virtual disks for your VM’s.  IDE is plenty good enough.

7. Thou shalt always use RAID controllers with at least 512MB of RAM on the board.

8. Thou shalt NOT use snapshots. Seriously. Stop doing that.

9. Thou shalt use Hyper-V as the ONLY role on your host OS.  Install no other roles nor features on your host server OS.  Except backup software.

10. Thou shalt never walk away from your host machine logged on. Once you are done with the console, log off.

 

ChaseChase Reitter
Network Consultant
Chase.Reitter@CustomSystemsCorp.com

 

 

 

© Copyright 2014 Custom Systems Corporation