Remote Desktop Error – An Authentication error has occurred – CredSSP encryption oracle remediation – SOLUTION

CredSSP encryption oracle remediation

CredSSP encryption oracle remediation

Error


We recently had an issue with remote desktop connection to a Windows 2012 server from a Windows 10 Pro client computer that was recently updated.

An Authentication error has occurred.
The function requested is not supported.
Remote computer: <servername>
This could be due to CredSSP encryption oracle remediation

CredSSP updates for CVE-2018-0886

Solution


We had to create a registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters; both the CredSSP and Parameters keys had to be created, and then create the AllowEncryptionOracle DWORD and give it a value of 2, worked for me on both Windows 7 and Windows 10 Pro computers. A reboot was not needed.
Registry path: HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters
Value: AllowEncryptionOracle
Data type: DWORD

Have Questions?


Leave us a comment or visit: https://southjerseytechies.net/

South Jersey Techies, LLC is a full Managed Web and Technology Services Company providing IT Services, Website Design ServicesServer SupportNetwork ConsultingInternet PhonesCloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.

Windows Server 2003 end of life guide

How to organize your migration from Windows Server 2003

 

Following on from end of support for Windows XP in April 2014, we are now rapidly approaching Windows Server 2003 end of life.

Despite Microsoft warning about end of life for Windows Server 2003 as early as April 2013, many organisations are yet to begin their migration away from the server platform. Worse still, many organisations and IT pros are unaware of the huge financial costs and security risks should they continue running Windows Server 2003 past the end of life date.

Reports from HP claim that more than 11 million systems are still running Windows Server 2003. With fewer than 240 days left until end of life, this a huge problem as the estimated time required to migrate a datacentre of 100 or more servers can range from a minimum of three months and upwards of 18 months.

If you own even one of those 11 million servers and you have yet to begin migration, you should be worried. Luck for you, the following guide will migrate you to a position of safety. We will cover the following:

• Windows Server 2003 End of Life date
• Understanding what end of support means for Windows Server 2003 and the associated impacts
• An outline of how to migrate Windows Server 2003
• Resources to aid migration

Windows Server 2003 End of Life date

According to the Microsoft Support Lifecyle section on 14 July 2015, Microsoft will end extended support on all versions of Windows Server 2003/R2.

Understanding what end of support means for Windows Server 2003

From then on, this means no more updates or patches from Microsoft, which can result a less secure and less stable infrastructure for your business. What this really means:

• Maintenance Costs – running legacy servers is expensive. Intrusion detection systems, advanced firewalls and network segmentation are required to protect a now vulnerable Windows Server 2003 platform. You will also have increasing cost from maintaining aging hardware. Current estimates in a TechNet post from Alex Fu place the cost of custom support post end of life at US$200,000 on average. In a Q&A with David Mayer, practice director of Microsoft Solutions for Insight Enterprises, he estimated a support cost of $1500 per server per year.

• No Updates – there will be no more updates to fix bugs, performance issues and security vulnerabilities. To put this into perspective, 2013 saw the release of 37 critical updates for Windows Server 2003/R2. Past the end of life date, these critical issues will remain unfixed leaving you open to cybersecurity dangers such as malicious attacks or electronic data loss.

• No Compliance – once support ends, your organisation will almost certainly fail to meet industry wide compliance standards. Regulations such as HIPAA, PCI, SOX & Dodd-Frank all require regulated industries to run on supported platforms. The impact is twofold: Non-compliance could result in the loss of business, while high transaction fees and penalties from non-compliance could dramatically increase the cost of doing business.

• Software and Hardware Compatibility Issues – new software and hardware devices will not be built to integrate with Windows Server 2003. Sticking with a legacy server means you will likely run into compatibility issues and may not be able to run new instances of software or communicate with the latest devices.

• No Safe Haven – without continued support from Microsoft, virtualized and physical instances of Windows Server 2003/R2 and Microsoft Small Business Server (SBS) 2003 will not pass a compliance audit.

How to migrate from Windows Server 2003

Do not underestimate the task that lies ahead. Migrating applications and server workloads is no easy task. Worryingly, a study by App Zero suggests that 62 per cent of organisations do not have a plan to upgrade or migrate, or even know that EOS is coming.

• Discover – first up is discovering and cataloguing all the software and workloads that are running on Windows Server 2003/R2 at present. Download the Microsoft Assessment and Planning toolkit as this will be a worthy support document.

• Assess – now you have a list it’s time to analyse and categorise all your applications and workloads based on type, criticality, complexity and risk. This helps you prioritise for migration as well as identify issues and opportunities.

• Target – in this step, you must choose a destination for each application and workload. This could be the perfect time to evolve your organisation to the next level and embrace the cloud. Microsoft offers a series of destinations for each application or workload which could include:

billionphotos-1008218 (1)

o Windows Server 2012 R2
o System Center 2012 R2 (Private Cloud)
o Microsoft Azure (Public Cloud)
o SQL Server 2014
o Office 365

• Migrate – now is the time choose a migration plan. Microsoft offers a fantastic Migration Planning Assistant which covers all four steps. Look for official Microsoft training courses to give you an in-depth understanding of the new platforms you are planning to migrate to.

Resources to aid migration

Due to the widespread requirement to migrate, there is a range of fantastic resources to aid migration. These include:

Microsoft Virtual Academy – arguably the largest and best collection of free self-study resources from Microsoft experts including videos, slide decks and self-assessments. Check out the section on migrating to Windows Server 2012, or the Microsoft zure JumpStart.

Windows Server 2003 Roles Migration Processdownload this document and turn it into an A3 poster, stick it on your wall and use it to visualise the whole process.

Microsoft Deployment Toolkitdownload this fantastic resource, which provides a collection of processes, tools and guidance for automating new desktop and server deployments.

Free Software Trials – Microsoft have a series of trials so you can check out the new software. Here they are:

Windows Server 2012 R2 trial
System Center 2012 R2 trial
Microsoft Azure one-month trial
Office 365 trial
SQL Server 2014 trial

Windows Server Migration Services – there are a series of organisations that offer assistance in migrating away from Windows Server 2003. Big players include:

• Dell
• RackSpace
• HP

Time is running out — start your migration away from Windows Server 2003 today. Fail to do so and you find yourself facing some organisation-crippling consequences

Have questions?

Our Business IT Server Migration Specialists in NJ, PA & DE are here to help.
Call us at: 856-745-9990 or visit: https://southjerseytechies.net/server-support/

South Jersey Techies, LLC is a full Managed Web and Technology Services Company providing IT Services, Website Design ServicesServer SupportNetwork ConsultingInternet PhonesCloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.

Upgrade to Windows Server 2012

10 Compelling Reasons to Upgrade to Windows Server 2012

Takeaway: Windows Server 2012 is generating a significant buzz among IT pros. Deb Shinder highlights several notable enhancements and new capabilities.

We’ve had a chance to play around a bit with the release preview of Windows Server 2012. Some have been put off by the interface-formerly-known-as-Metro, but with more emphasis on Server Core and the Minimal Server Interface, the UI is unlikely to be a “make it or break it” issue for most of those who are deciding whether to upgrade. More important are the big changes and new capabilities that make Server 2012 better able to handle your network’s workloads and needs. That’s what has many IT pros excited.

Here are 10 reasons to give serious consideration to upgrading to Windows Server 2012 sooner rather than later.

1: Freedom of interface choice

A Server Core installation provides security and performance advantages, but in the past, you had to make a commitment: If you installed Server Core, you were stuck in the “dark place” with only the command line as your interface. Windows Server 2012 changes all that. Now we have choices.

The truth that Microsoft realized is that the command line is great for some tasks and the graphical interface is preferable for others. Server 2012 makes the graphic user interface a “feature” — one that can be turned on and off at will. You do it through the Remove Roles Or Features option in Server Manager.

2: Server Manager

Speaking of Server Manager (Figure A), even many of those who dislike the new tile-based interface overall have admitted that the design’s implementation in the new Server Manager is excellent.

One of the nicest things about the new Server Manager is the multi-server capabilities, which makes it easy to deploy roles and features remotely to physical and virtual servers. It’s easy to create a server group — a collection of servers that can be managed together. The remote administration improvements let you provision servers without having to make an RDP connection.

3: SMB 3.0

The Server Message Block (SMB) protocol has been significantly improved in Windows Server 2012 and Windows 8. The new version of SMB supports new file server features, such as SMB transparent failover , SMB Scale Out, SMB Multichannel, SMB Direct, SMB encryption, VSS for SMB file sharing, SMB directory leasing, and SMB PowerShell. That’s a lot of bang for the buck. It works beautifully with Hyper-V, so that VHD files and virtual machine configuration files can be hosted on SMB 3.0 shares. A SQL system database can be stored on an SMB share, as well, with improvements to performance. For more details about what’s new in SMB 3.0, see this blog post.

4: Dynamic Access Control (DAC)

Even though some say Microsoft has shifted the focus away from security in recent years, it would be more accurate to say it has shifted the focus from separate security products to a more “baked in” approach of integrating security into every part of the operating system.

Dynamic Access Control is one such example, helping IT pros create more centralized security models for access to network resources by tagging sensitive data both manually and automatically, based on factors such as the file content or the creator. Then claims based access controls can be applied. Read more about DAC in my “First Look” article over on Windowsecurity.com.

5: Storage Spaces

Storage is a hot — and complex — topic in the IT world these days. Despite the idea that we’re all going to be storing everything in the public cloud one day, that day is a long way off (and for many organizations concerned about security and reliability, it may never happen). There are myriad solutions for storing data on your network in a way that provides better utilization of storage resources, centralized management, and better scalability, along with security and reliability. Storage area networks (SANs) and network attached storage (NAS) do that, but they can be expensive and difficult to set up.

Storage Spaces is a new feature in Server 2012 that lets you use inexpensive hard drives to create a storage pool, which can then be divided into spaces that are used like physical disks. They can include hot standby drives and use redundancy methods such as 2- or 3-way mirroring or parity. You can add new disks any time, and a space can be larger than the physical capacity of the pool. When you add new drives, the space automatically uses the extra capacity. Read more about Storage Spaces in this MSDN blog post.

6: Hyper-V Replica

Virtualization is the name of the game in the server world these days, and Hyper-V is Microsoft’s answer to VMware. Although the latter had a big head start, Microsoft’s virtualization platform has been working hard at catching up, and many IT pros now believe it has surpassed its rival in many key areas. With each iteration, the Windows hypervisor gets a little better, and Hyper-V in Windows Server 2012 brings a number of new features to the table. One of the most interesting is Hyper-V Replica.

This is a replication mechanism that will be a disaster recovery godsend to SMBs that may not be able to deploy complex and costly replication solutions. It logs changes to the disks in a VM and uses compression to save on bandwidth, replicating from a primary server to a replica server. You can store multiple snapshots of a VM on the replica server and then select the one you want to use. It works with both standalone hosts and clusters in any combination (standalone to standalone, cluster to cluster, standalone to cluster or cluster to standalone). To find out more about Hyper-V replica, see this TechNet article.

7: Improvements to VDI

Windows Terminal Services has come a long way, baby, since I first met it in Windows NT TS Edition. Renamed Remote Desktop Services, it has expanded to encompass much more than the ability to RDP into the desktop of a remote machine. Microsoft offered a centralized Virtual Desktop Infrastructure (VDI) solution in Windows Server 2008 R2, but it was still a little rough around the edges. Significant improvements have been made in Server 2012.

You no longer need a dedicated GPU graphics card in the server to use RemoteFX, which vastly improves the quality of graphics over RDP. Instead, you can use a virtualized GPU on standard server hardware. USB over RDP is much better, and the Fair Share feature can manage how CPU, memory, disk space, and bandwidth are allocated among users to thwart bandwidth hogs. Read more about Server 2012 VDI and RDP improvements here.

8: DirectAccess without the hassle factor

DirectAccess was designed to be Microsoft’s “VPN replacement,” a way to create a secure connection from client to corporate network without the performance drain and with a more transparent user experience than a traditional VPN. Not only do users not have to deal with making the VPN work, but administrators get more control over the machines, with the ability to manage them even before users log in. You apply group policy using the same tools you use to manage computers physically located on the corporate network.

So why hasn’t everyone been using DirectAccess with Server 2008 R2 instead of VPNs? One big obstacle was the dependency on IPv6. Plus, it couldn’t be virtualized. Those obstacles are gone now. In Windows Server 2012, DirectAccess works with IPv4 without having to fool with conversion technologies, and the server running DirectAccess at the network edge can now be a Hyper-V virtual machine. The Server 2012 version of DA is also easier to configure, thanks to the new wizard.

9: ReFS

Despite the many advantages NTFS offers over early FAT file systems, it’s been around since 1993, and Windows aficionados have been longing for a new file system for quite some time. Way back in 2004, we were eagerly looking forward to WinFS, but Vista disappointed us by not including it. Likewise, there was speculation early on that a new file system would be introduced with Windows 7, but it didn’t happen.

Windows Server 2012 brings us our long-awaited new file system, ReFS or the Resilient File System. It supports many of the same features as NTFS, although it leaves behind some others, perhaps most notably file compression, EFS, and disk quotas. In return, ReFS gives us data verification and auto correction, and it’s designed to work with Storage Spaces to create shrinkable/expandable logical storage pools. The new file system is all about maximum scalability, supporting up to 16 exabytes in practice. (This is the theoretical maximum in the NTFS specifications, but in the real world, it’s limited to 16 terabytes.) ReFS supports a theoretical limit of 256 zetabytes (more than 270 billion terabytes). That allows for a lot of scaling.

10: Simplified Licensing

Anyone who has worked with server licenses might say the very term “simplified licensing” is an oxymoron. But Microsoft really has listened to customers who are confused and frustrated by the complexity involved in finding the right edition and figuring out what it’s really going to cost. Windows Server 2012 is offered in only four editions: Datacenter, Standard, Essentials, and Foundation. The first two are licensed per-processor plus CAL, and the latter two (for small businesses) are licensed per-server with limits on the number of user accounts (15 for Foundation and 25 for Essentials).

To View Full Article Click Here