The End of Life for Windows 7, Server 2008 R2, & Small Business Server 2008 + 2011

End of Life Windows 7, Server 2008 R2, & Small Business Server 2011

Microsoft has announced that its support for Windows 7, Windows Server 2008 R2, and Small Business Server (SBS) 2011 will be coming to an end on January 14, 2020.

What does that mean for you? First, security patches and updates will no longer be implemented, leaving Windows 7 workstations and servers susceptible to security breaches. On January 13, 2015, Microsoft ended mainstream support for Windows 7, but now extended support is ending as well. Extended support is still safe to use until 2020 currently. Normally Microsoft would add new features during the mainstream support phase, but they will not be being doing this anymore. They will however, continue to patch any security treats. South Jersey Techie’s strongly recommends upgrading your business’s servers and workstations before the January 2020 deadline- and to start planning now to avoid the urgency of the deadline. Businesses in the healthcare industry will be impacted by the changes in relation to HIPPA violations if their server isn’t updated before the deadline. The deadline will be here before you know it and updating an IT infrastructure is a large task and shouldn’t be put off until the last minute.

What are the next steps for your business? Many of our clients are starting to upgrade now or are planning to include the upgrades in their 2019 budget. Send us an email or give us a call and we will evaluate your line of business software for Windows 10 and upgraded server compatibility. If your company decides to upgrade its old server and workstations to meet the January 2020 deadline, South Jersey Techie’s has the reliable solutions and experienced technicians you need for managing the data migration and even the retired hardware. You can have peace of mind knowing your old data will be securely erased and destroyed.

Unsure if this deadline will affect your business? South Jersey Techie’s can review your server for you and determine its end of life date or if it will be affected by the 2020 end of support date. If you have any questions or concerns about your office and the 2020 end of support date, please give us a call today: (856)745-9990.

GET STARTED WITH A NEW WINDOWS 10 PC

Can’t Find What You’re Looking For?


Microsoft hints at September release of Windows 10’s next feature upgrade

Based on the current progress for Windows 10 version 1903, due to arrive next spring, it now looks like the fall update for the OS will arrive around Sept. 10 or Sept. 24.

Microsoft last week released the first preview of what will become Windows 10 version 1903, the opening feature upgrade of next year, slated to ship in the spring.

The debut of what Microsoft calls the “Skip Ahead” build for Windows 10 1903 also hints that the release of this fall’s upgrade, aka 1809, will take place in September. If so, it would be the first time since late-2015 that the actual delivery date matched the numerical label.

On July 25, Microsoft forked the 1809 preview of Windows 10 – as it’s done before when a feature upgrade approaches – so developers could continue to deliver betas for that build while also beginning to work on the next-in-line, 1903. (Microsoft uses a yymm labeling system to mark its Windows 10 feature upgrades; 1809 should indicate a September 2018 release, while 1903 would be a March 2019 release.)

When it forks preview code, Microsoft provides the even-further-in-the-future build, in this case, 1903, to Windows Insider participants who earlier volunteered for Skip Ahead. As the current feature upgrade gets close to release, Microsoft switches Skip Ahead users to the following upgrade, so that engineers can start collecting feedback on that version even as they keep polishing the one set to launch soon. The bulk of Insiders remain on the latter.

Think of the Skip Ahead debut as a warning bell, like the one rung at track meets when racers start the final lap: When Microsoft begins to ship Skip Ahead code, it’s close to wrapping up the impending feature upgrade.

In 2017, as Windows 10 1709 (aka “Fall Creators Update”) neared completion, Microsoft first forked the preview code and distributed a different build to Skip Aheaders on Aug. 31. Windows 10 1709 began its release cycle on Oct. 17, or 47 days later. With this year’s version 1803, Skip Ahead debuted Feb. 14, or 75 days before the April 30 release of that upgrade.

(Windows 10 1803’s original launch date, reportedly April 10 – which was one of two dates Computerworld had forecast in February – was postponed by 20 days after a deal-breaking bug was uncovered at nearly the last minute.)

For one estimate of the release date for Windows 10 1809, Computerworld added 47 days to July 25, arriving at Sept. 10. A second estimate was generated by adding 61 days – the average of the two previous Skip Ahead triggers – to July 25, resulting in a Sept. 24 rollout.

Because the last three feature upgrades launched on either a Monday or Tuesday – April 11, 2017 for version 1703; Oct. 17, 2017 for 1709; April 30, 2018 for 1803 – Sept. 10 or 11 would be the most likely release dates for 1809, absent a show-stopping problem like the bug before 1803’s launch. Computerworld’s alternate forecast would be September 24 or 25, also a Monday/Tuesday combination, because it would match the previous upgrades’ average time-between-Skip-Ahead-and-release.

If Microsoft does release Windows 10 1809 in September, it would be the first time since November 2015 that the company has matched delivery date and the upgrade’s label. Version 1511 debuted Nov. 10, 2015. The four subsequent upgrades, 1607, 1703, 1709 and 1803, all missed their release months by between 2 and 30 days. (Version 1607 came the nearest, releasing Aug. 2, 2016.)

Although Microsoft has never expressly tied itself to March and September release months – in a support document, it gives itself wiggle room by stating that feature upgrades will be released “twice per year, around March and September [emphasis added]” – the disconnect between release and numerical designation has always seemed odd.

Issuing feature upgrades during the appointed months would be a sign that Microsoft has gotten a better handle on the rapid development tempo it has at times struggled with executing. It would also be a step toward a more predictable schedule, which was the point of the pledge it made over a year ago to issue a pair of feature upgrades annually.

Delete WINDOWS.OLD on Windows Server

 

After performing an in-place upgrade on a Windows machine, you will find a WINDOWS.OLD folder in the root of C:. This folder will have a backup of your old program files, appdata and Windows folder… just in case you need to revert back or recover something that might have been lost during the upgrade. When you try to delete it though you are told you don’t have permissions. Just a small point here, it is generally not recommended to do in-place upgrades on servers. In fact there are some products (e.g. Exchange, ConfigMgr) that explicitly state they do not support upgrading the Operating System. There is of course a difference between “what works” and “what is supported”, but we do suggest where possible you do a clean Server install and migrate your application to the new server. Anyway, let’s assume you’ve understand all the risks and have done a successful in-place upgrade, you now find the old WINDOWS.OLD folder of several GB in size sitting there. If all is well, then you might as well just delete it.

SOLUTION

On Desktop OS version, you can just use the disk cleanup tool to remove it, but that is not available (by default) on Servers, so there are a couple of approaches.

Command line tools to take ownership and delete the folder. Make sure to “run as administrator”

How can I delete the windows.old from an upgraded Windows Server?

For a client OS that’s upgraded, the Disk Cleanup utility can be used to delete the very large windows.old folder containing the old OS. This isn’t available on a server OS without installing the Desktop Experience feature.

To delete, it is necessary to take ownership of the folder, give administrators full control, then delete. This can be done with the commands below:

  •  takeown /F c:\Windows.old\* /R /A /D Y
  •  cacls c:\Windows.old\*.* /T /grant administrators:F
  •  rmdir /S /Q c:\Windows.old

 

Or you can add the “Desktop” features to provide the Disk Cleanup tool:

Step By Step Guide to Enabling “Disk Cleanup Utility”

1. Open The Roles and Features Wizard

To open the roes and feauture wizard. Lauch the “server manager” by pressing the Windows key

and clicking on the server manage please see Screenshot as shown.

Personally, the command line option is less messy and saves having to add features to your server that don’t really need to be there.

2. Click on Add role and Feature

Click on add role and feture to launch the add role and feature wizard.

3.  Choose installation Type

Choose rolebase or feature based installation to install to local machine.

4. Click Next all the way to features

Click “next” all the way to features. Locate “User Interface and Infrastructure”. Click on “Desktop Experience”

and install additional required feature.

5.  Proceed with the installation and Reboot

Make it sure that you reboot the system

6.  Verify that the Utility is indeed installed

Ready to run diskcleanup. See screen shot below.

Disk Cleanup in Action

Below is a sample snapshot of disk cleanup in action.

10 Windows 7 tips to get the most out of your machine

If you’re one of the many business users who has not upgraded their computer to Windows 10, there are still resources to boost your experience. Here are 10 tips for getting the most out of the OS.

Windows 10 faced a controversial roll-out, with privacy concerns, bugs, and other issues plaguing many users. And as of August 2016, just 1% of business machines had upgraded to Windows 10, according to a study from Softchoice. Instead, 91% of the machines were operating with Windows 7—an 18% increase over the same period of time in 2015.

“It seems businesses don’t see an urgent need to move operating systems, so long as their cloud-based applications are still running fine on Windows 7,” Softchoice’s Microsoft director Craig McQueen wrote in a press release at the time. “In addition to the security benefits, I think once organizations grasp the user benefits—such as touch and Cortana—we will start to see a boost in adoption.”

While experts predict Windows 10 deployments will pick up this year, it’s important for those still using Windows 7 for business to get the most out of their machines. Here are 10  articles with Windows 7 tips that will help enterprise users operate the machines more effectively.

Read More

10 Windows 7 commands every administrator should know

The command line is often the best place to resolve Windows 7 desktop problems. These basic commands will help speed your troubleshooting tasks.

PC troubleshooting is becoming less common in larger organizations, but consultants and techs in smaller shops still have to get their hands dirty identifying and fixing desktop problems. Oftentimes, troubleshooting Windows 7 means delving into the command line. Here are 10 fundamental Windows 7 commands you might find helpful.

Read More

10+ Windows 7 services you may not need

If you evaluate your organization’s need for certain Windows 7 services, you may find that a number of them can be safely disabled.

Every version of Windows has shipped with a core set of system services that must run so that the system can perform basic operations. However, your organization may not necessarily need to have all the services running, and disabling unnecessary services can enhance performance and security. We’ve put together a list of 13 services you can disable on your Windows 7 systems that will probably not negatively affect your business operations at all.

Before you take drastic action, such as disabling a service on every PC in your organization, make sure that the service you’re disabling is not actually in use. This article makes a couple of broad assumptions: that your company doesn’t need to share Windows Media files and doesn’t use Windows 7’s HomeGroup features.

This is not a definitive list of services that can be disabled; these are just some obvious ones. Read carefully and make sure you test changes before deploying them across your organization.

Read More