Enterprise Server Strategies for the CIOEmail Alerts
-
Building an automated permissions management solution with Icacls
Using basic Icacls syntax, admins can create an automated solution to ensure correct network file permissions at all times. Tip
-
Top tools for fixing Windows NTFS corruption issues
There are several utilities out there designed to salvage NTFS data and restore your hard disk, but even the best ones have pros and cons. Tip
-
Icacls syntax basics: Automating Windows file permissions
Believe it or not, the Icacls tool in Windows can be used to create a fully-automated permissions management solution – once you understand the basic syntax. Tip
-
Open source distributed file system (DFS) solutions go beyond Windows
Even though DFS is commonly linked to Windows Server, there are several other non-Microsoft options out there as well – and they're free. Tip
-
The compliance benefits of Windows identity and access management
A sound identity and access management strategy is key to keeping regulators off your back. Here are six ways IAM factors into the compliance equation for Windows environments. Tip
-
Monitoring Windows DFS health with diagnostic reports
Windows Server 2008 features new reporting capabilities to help admins stay one step ahead of potential DFS replication problems. Tip
-
Standalone versus domain-based namespaces in Windows DFS
When setting up namespaces in Windows DFS, be aware that the popular choice may not be the best fit for your environment. Tip
-
The anatomy of a Distributed File System namespace
Namespaces in DFS present users with a centralized view of file server resources. This article dissects the basic components of a DFS namespace. Tip
-
An introduction to dynamic storage provisioning for Windows
Administrators can and save money reduce wasted disk space by implementing dynamic server provisioning in their environments. Tip
-
Using DFSR for SYSVOL replication in Windows Server 2008
With the release of Windows Server 2008, admins can now use DFSR for SYSVOL replication (instead of FRS). The catch? A tricky migration process when upgrading from Windows Server 2003. Tip