Patrickv

I hope to get a video in the pipeline which closely match to your question. If it's one student and you have active directory you will have few options available to limit that one student by logon hours and a list of computers that student is or not allowed to login into. Here is our YouTube channel where you can find some active directory how to videos. But sadly I don't have the video produced yet on to show how to do demonstrate as described above. https://www.youtube.com/c/PvcomputersNZ

I think I have a New Zealand one posted some where on Pvcomputers for those kiwi's on here. https://www.netsafe.org.nz/

That sounds stupid. They are trying to get many people on and use Windows 10 as possible and doing that is like shooting themselves in the foot. lol

How did I miss this forum, lol Well I am Patrick I am from New Zealand and I run a website where we have videos and content to help people with computers.

Most Likely your exchange and sql server would bloat that if you have it.

Hmm. What exchange server are you using? Here are a few troubleshoots to help you? 1) Check your incoming filtering or blacklist. 2) Reboot exchange server. That's what i can think of at the moment that might help Regards, Patrick

Hmm, I am wondering if the full backup (NTBackup) has overwritten something on the clean install. NTLDR is the OS bootloader, That's what you need to find out if you get their or you don't. Here some more things I could think off 1) Does your server reach that black screen and reboots and keeps looping through that 2) Have you tried F8 safe mode 3) Have you tried repairing the operating system with OS disk

If you are using it as a member server, i don't see any problem with it as long you don't use it for anyhthing releated to Domain Controllers, Global Catalog etc. I would not recommend using Server 2003 SBS because that might cause issues. Well That's what i know, but other members might add what i have missed. Regards, Patrick

You do have a good point but I am not sure. I think you can't it from GPO, I could be wrong. I would normaly do this on device and hardware level. eg Disable the sound card and have sound card working in staff room which only staff use.

What is MIS? Firstly if you can't access the server remotelly you should do your standard network troubleshooting 1) Check NIC is working 2) Check Network cable 3) Check switch etc...

Remote Desktop Connection purhaps, I have seen an example of a domain user login into a server remotely.

So you did a clean install of Windows Server 2003 on new Hardward and then restore data from the old server to the new server with new hardware. Here is Some troubleshoots 1) Did you test the clean install server before restoring the data. 2) What did you restore and how. 3) Check if your boot partion is active and primary. 4) Check your bios boot order settings. 5) Check your RAID contoroller boot settings and configuration. I hope this narrow down some points for ya. Regards, Patrick

You need to narrow it down. 1) Do certain users or all users have this issue. 2) Are you using roaming profiles. 3) Create a new dummy user and check if replicate this isssue 4) Try removing the profiles locally on the machine. NOTE: Please do not delete the profile directly in the users folder otherwise will cause Temp profile isssue. Try that using what above to narrow it down. That's what i can think of atm. Regards, Patrick

In my personal opinion Wireless is not a good practice for domain login from Alt+Ctrl+Del to desktop. Wireless has limits on distance and concurrent usage and which would lead to your problem. If you have issues when you have eth cables plugged in then it's another story. I am thinking what Synack said seems resonable, Don't forget to throw roaminng profiles in the mix if use those because they are the biggest data transfer issue.

Is this an isolated incident to one user, or is affected on all users, Because that is odd and sneaky to hide stuff like that.