Category: Microsoft

Windows 2012 Registry Problem

Windows 2012 ServerHere is something that I came upon recently in regards to Windows Server 2012 and performance issues. My home server runs Windows 2012 Server Essentials and the operating system is installed onto a Samsung 830 SSD. Performance was becoming a problem of lately. There were noticeable lag in opening up drives in Windows Explorer and other slight delays that I thought were related to the SSD drive. SSD drives can become slower as they near capacity. Even if you delete a lot of large files to free up space, the trim feature still needs time to run and free up space. This means that if you have an SSD at 85% capacity and you delete files to bring it down to 50%, the SSD still has 85% allocated until the trim feature has a few hours of uninterrupted time to run.

After further investigation, I found that trying to open Control Panel – Hardware – Devices and Printers would not even display at all. Next I looked at Device Manager to see if there were any issues there. I did not see any problems with items listed in Device Manager. However after clicking on View – Show Hidden Devices, I found thousands of entries for Storage Volume Shadow Copies and the same for Storage Volumes. There were also a large number of USB devices that I had used in the past. The Windows registry stores all these previous entries and over time, never removes them. I uninstalled the old USB devices, but for the shadow copies and storage volumes, I found that this problem is most likely due to normal usage of Remote Desktop and other Windows services. To remove them manually would take a very long time.

Microsoft has a utility for this issue. Microsoft DevNodeClean can be run on Windows Server 2003 and newer operating systems. In fact, you will need to most likely run this utility weekly if the issue persists. To run the command, use an elevated CMD Prompt and type:

devnodeclean /n

After restarting the server, this resolved the performance issues and I could open up Devices and Printers again.

Filed under: WindowsTagged with:

Backup Strategy For Project Managers

drive iconBackups are a necessary routine for computers. Over the years, there has been many trends in computing that promised to make backups easier, simpler, but as humans, we still tend not to do a good job when it comes to backing up our data. The best solution for home users is Time Machine in Mac OS X. Simply add a drive (usually an external drive), and setup Time Machine to backup your entire main drive. Time Machine is the most simple backup to setup, but it is not perfect. After multiple backups, Time Machine usually encounters problems and the easiest solution ends up having to wipe your Time Machine drive and start all over again. On Windows, there are third party apps that allow for Time Machine like backups. Their main benefit is that their user interfaces are easier to use than the built-in Microsoft Backup program. There are also cloud backups as well now, so you can use iCloud, Google, Microsoft, or Dropbox for your backups. For most of us though, the cloud backup should really be a secondary backup and not your primary. In general terms the advice is to have a backup plan and to automate it as much as possible. Eventually all hard drives and flash memory fail in some way, and so backups are always going to be needed.

As a project manager, one backup strategy that I have used for a number of years is to have a one folder backup strategy. For my business laptop, I create one folder under C:\Users\Username\My Documents\. This folder I name Projects and I then create a shortcut for it and place the shortcut on my Desktop. For every project I work on I create a folder underneath the Projects folder. As I complete projects, I then move these folders to \Projects\Archive. Anything related to a project has to be save somewhere under the Projects folder. This takes discipline, but is very easy to do once you keep to this routine of saving files to one folder.

OS X Disk Error

Although every Operating System now provides a directory structure for users, most people have made the Downloads folder their main working folder! How many times has someone asked you to help them find a file, and you have opened their Downloads folder to discover thousands of files? This happens way to often. The Downloads folder was never meant to be a work folder. It was mean to help users find their downloaded files, but over time, people have treated the Downloads folder as their main repository for everything. It is important to remember that the Downloads folder is really a temporary folder for files. Nothing important should ever exist in the Downloads folder. Anything in the Downloads folder can and should be deleted. Move all your important files and working files to your main Projects folder and never work on any files outside of the Projects folder.

Now that you have all your files in one location, you need to copy your Projects folder and anything underneath to a secondary drive, backup location, cloud service. Although at the end of the day, you could simply copy and paste, drag and drop, it is best to automate this. In a business environment, there usually is a network drive or NAS that you can backup important files to. There are multiple apps or commands that you can script to accomplish this. The easiest way I have found is to use SyncBackSE. Using this application, I automate the backup of the Projects folder to run Monday through Friday, while I am at lunch. This backup strategy works well and is uncomplicated to use.

Filed under: Microsoft, Project Management, Tech Notes, WebKeyDesign

Mac OS X 10.9 Mavericks SMB2 and Windows 2012 Essentials Server

Apple LogoApple has a long history with computer networking, from AppleTalk to today’s Internet connected world. However, it is Windows networking that still causes all kinds of headaches for Mac OS X users. It seems that with every release of Mac OS X, Apple seems to have recurring issues with Windows shares. Some of Apple’s defenders will state that Apple adopts industry standards as is, and it is Microsoft and others who publish specs, but don’t actually follow them, so when Apple does follow the specs, it seems to just end up breaking things. SMB is the networking protocol that Microsoft uses for Windows networking. It is what allows Windows network file shares to work across the network. With the latest versions of Mac OS X, Apple abandoned the open source SAMBA package that most Linux distros use to connect to Windows, and wrote their own SMB2 software. This makes Mac OS X 10.9 Mavericks connect faster and better to Windows servers. Well that is when it works!

SMB Connections Fail

There is one Windows 2012 Essentials server with multiple shares. There are two Macs on the local network. One iMac is connected over Wireless N and one MacBook Pro is using a wired ethernet 1Gb connection. When using the Connect to Server… option the iMac connects fine and has no issues. The MacBook Pro opens the share and then never displays any files, it just spins in the lower left hand corner of the window that opens. Both computers are running Mac OS X 10.9.3 Mavericks.

Mac OS X SMB Connect to Server

Connecting via CIFS instead of SMB seems to work for the MacBook, but it is slower.

The Solution

The solution ended up modifying the Windows 2012 Essentials server. There are two registry keys that need to be added in order to fix the problem for the MacBook.

Under this Registry Key:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Add these DWORD values:

  • Smb2CreditsMin – make this 768
  • Smb2CreditsMax – make this 16384

Once you made the changes restart the Windows Server and then the Macintosh clients. It should now fix the problem.

Microsoft provides the following information on these registry keys:

The defaults are 512 and 8192, respectively. These parameters allow the server to throttle client operation concurrency dynamically within the specified boundaries. Some clients might achieve increased throughput with higher concurrency limits, for example, copying files over high-bandwidth, high-latency links.

Filed under: Apple, Mac OS X, Networking, Windows