Let me begin by saying that I am not qualified to be in this forum. I would say that I am a highly experienced Windows user (thru version 7), but when it comes to networking I am out of my depth. But I teach basic computer courses at a small school
on the border of the Dominican Republic and Haiti and am the best they have to try to maintain their server (originally installed by IT pros).
The basic network is the following:
- Server: Windows Server 2012 Standard (Version 6.2.9200)
- Desktops: Windows 8 Pro 64 (Version 6.2.9200)
The probable cause of the problem: Electricity here is *mostly* stable but we only have electricity about 14 hours a day and the changeover time is not consistent. The voltage is not always steady either - sometimes it comes in quite low and sometimes
it comes in dangerously (to electronic equipment) high. The result is that we often lose power in the middle of class (at times several times because *mostly* stable means that at times it is not stable). I have lost 2 power supplies (out of 25) due
to this issue.
The server, even with a UPS, has regular hard power offs due to power outages when no one is able to get to the lab quick enough to power it down or to get the generator powered on. I am reasonably sure that one of the more recent dirty shutdowns has
cause the problem.
The problem: all of the shared networks drives are "broken".
I realize that not all of this will be helpful, but better too much than too little information. Here is what I can tell you with my limited knowledge:
- The shares are being done thru Group Policy.
- There is no login script being utilized for users.
- The home folder in Group Policy is \\ server-01\students\8\%username% and it is being assigned as drive "S" for each student. (space after the \\ to prevent this forum from preventing my post because it thinks I am posting a link)
- The physical path to the shared "students" in the line above is E:\shares\users\students.
- On booting any of the desktops with the server already booted, there is a long delay before Windows finally loads. It is clearly timing out on attempting to login to the server and pull the roaming profile. The end result is that users are being
assigned temporary profiles.
- Remote desktop into the server does not function
- If I login *on* the server console itself, the shared network drive "S" DOES get assigned correctly.
- Profile are stored in E:\shares\profiles
- I have browsed Event Viewer and have seen only two errors. One is due to a backup driver being normally powered down while the backup service is always initialized on boot. The other was DFSR Event 2213 due to a dirty shutdown. This error
has been resolved. There are a few warnings, but nothing that seems on point for this issue.
- In Event Viewer, I do see Event ID 1003 - Start processing GPOs. But since the "S" drive is assigned when booting from the system console, we knew that the GPOs are getting processed.
I am hoping that there is a very simple resolution to this issue and that one of you kind folks can give me instructions on how to do it, or guide me to helping you find additional information on the issue.
Many thanks.