Windows Server

Windows Server

Troubleshooting slow AD logon

Issue: you are getting complaints from some or all users that their logon's are slow in a MS Active Directory environment Information gathering: 1) Are you using roaming profiles 2) Do you have multiple sites Solutions and what to look at: If you are using roaming profiles, check the following: - profile size of the end user, to check this open properties of the end users profile folder on the server.  If it is large, use treesize or another tool to see what is taking up all the space in the Read more [...]

Migrate SBS 2008 to Windows 2012

Issue: You have an existing SBS 2008 environment and you need to migrate to Windows 2012.  In addition, you may be migrating the built-in Exchange 2007 instance to Exchange 2013 or to Office 365. Purpose: I will provide a high level overview of the options and process and then link to more granular steps  for the solutions.  I will continue to update this as I have time including additional steps. Key questions that determine decisions: How many end users do you have? Do you want to: A) Read more [...]

prevent CHKDSK checking disk volume at boot

Issue: You need to disable CHKDSK from running on a volume at boot if it detects a dirty bit. Background: at boot time, CHKDSK performs a default boot-time chk.  If a 'dirty bit' is found, CHKDSK runs a full scan CHKDSK of the disk during boot. Solution: Several articles suggest editing the registry, however the best way to gracefully update the setting and corresponding registry key is to issue the following command prompt command which will in this example disable auto check (autochk) from Read more [...]

Windows default NTFS file permissions

I recently moved a VMDK from one server to another, this was a mistake as I got access denied to files inside it.  I messed around with it and ended up making matters worse and getting access denied to the volume itself because permissions were in an inconsistent state from my attempting to set permissions then canceling.  I then had to move the VMDK back to the original server and set the permissions back to default as they were jacked up even on the original server with its VMDK back in place Read more [...]