Unfortunately, Windows Server 2008 R2 Standard Edition has limitation of 32GB of RAM. Too bad, if more memory is needed. When I have run into this issue, I have decided to upgrade OS to Enterprise Edition. We have VLK license that supports both Editions, so I did not expect any issues with this.
It’s hard to believe but I have recently needed to execute the in-place upgrade from Windows 2000 to Windows 2003. Nothing special, but in the middle of the copy process the installer threw out the error:
Setup Cannot Copy the File Cmprops.dl_
I could see the file on CD, but could not copy it. OK, I ignored the message and immediately got another one about the next file. Well, the setup was cancelled.
From Windows 2008 to Windows 2012 the robocopy utility has been changed. Now it detects all files an “modified”.
I use robocopy to bring data from remote office to the centralized file server and back them up further. I’m not sure if robocopy actually copies files or just changes some attributes, but NetBackup sees the files as new and back up all of them even during incremental backup.
After battling the issue on my own I have opened a case with Microsoft. Together with MS engineer we have found two potential solutions
Honestly speaking I do not know when exactly it happened and why, but one day I found out that the Windows Firewall service on my computer was stopped. Not a big deal, I tried to start it up and got the Access Denied error. Read the rest of this entry »
Some DFS-related errors, such as “Cannot enumerate namespace“, “Element not found” or “RPC server is not available” are related to the configuration issues in namespace. All DFS components in registry, Active Directory and file system should be in sync. If they are not, the mentioned above errors happen. Pretty often it is easier and faster to remove DFS namespace completely and recreate it rather than to fix it. This article is about removing a DFS namespace and cleaning up all its components.
Cannot log into remote system due to time discrepancy?
Once I received a request to fix an issue with MAC computers that could not access any shared folders on Windows file server. The Windows clients were OK. Well, the very first troubleshooting step is to log into the server. However, I could not do this. I got a message saying that domain controller was not available and my credentials could not be verified.
It looked like this server could not find a domain using the DNS servers in its IP configuration. But how to check and modify it?