I have 4 domain controllers and 3 of them are pointing to the fourth as the time server. I am taking this fourth server offline and need to move the time server to one of the other three.  How do I change the time server to another domain controller?

We are currently upgrading a network to a 2016 Terminal services environment. There are some legacy applications that is not compatible with 2012 or 2016 and needing to keep some applications on a 2008 R2 machine.

We've attempted to add the session host from the 2016 wizard as the server does appear to be discovered. There is a compatibility message mentioning that it must be running at least Windows Server 2016.

Wondering if anyone has been able to get a 2008 server added and running in a 2016 farm so the apps can be published? Or have some alternative solutions?

Thanks,
compat-ss.PNG

Just the last couple of days our 500+ WSUS clients go straight to

Error 8024401f

The WSUS server 2012r2  has been rebooted, and appears to be OK, syncs updates from MS etc. It will not even update itself from itself.

Can anyone please advise?
Thanks

I need help in creating a windows powershell for win server 2008 and 2012 R2 to check the following:

When i run the powershell on the server, it will return if this server is running:
 - Cluster Service or
 - Failover Clustering service enabled/ configured or
 - has any registry keys to indicate that it is part of a cluster

If I purchase a VL of Server 2016 Standard will it include downgrade rights for Server 2008 R2?
I think the answer is yes.
More importantly, once I register it with VLSC, will VLSC give me a 2008 R2 download link and an actual 2008 R2 key?

I know downgrade rights usually go back forever but using the new key rather than reusing an old key in important to me...for some reason.

I was thinking the VLSC gave you keys up to 2 versions back, but wasn't sure if the  2012 and 2012R2 counted as the two versions back, or if I could get a key going all the way back to Server 2008.

Recently when we add a new computer to our network and try to do the windows updates we get the error 8024402c.   The computer is not added to the domain yet so it's not a GPO problem.  We also noticed that the Windows Server 2008 R2 have the exact same problem.

The Win 2012 R2 servers are getting updates fine.

The new computers have nothing installed on them yet.  e.g. no anti-virus, etc.

Hi Experts

thanks for your in advance.

problem definition:
I have only 1 Active Directory server with DNS integrated in an isolated network and I want all DNS queries to be made to itself only so no DNS queries are broadcasted.
AD is imported from PROD environment and previously serving multiple zones and multiple different VLANs.  I now need to use this imported AD DNS server to not to forward any broadcast queries to different DNS servers.

reasons: Server is imported from PROD  environment so whatever the IP details it has in DNS tab should change I believe. it currently have multiple IP addresses listed primary and secondary DNS

options:  
a)should I only set up one DNS server IP which would be the itself 127.0.0.1 as primary DNS server and that's it leave the rest with no config. only 1 DC in this isolated environment which holds all the FSMO roles and  has no connections to PROD.
b) should set new port forwarding on Pfsense firewall to forward all DNS queries to  127.0.0.1

thanks for the help

How do I add the GPO tools for Windows10 (1703) to my 2008r2 Domain Controller?   Is it safe to add the ADMX file to the server?  What is the process once the msi file for the ADMX is downloaded to get them into the Policy Editor?

Thanks

Hello all,

Recently a Windows 2008 server is displaying the following message  

"please wait for the system Event Notification service"

This issues occurs this morning, A user will go and log off and he will get "Please wait for the System Event Notification Service..." on his screen.

I try and manually log the user out from task manager and even tried to reset the connection from Remote Desktop Services Manager .

Please kindly advise........
maxresdefault.jpg

After a failover an entire folder that was previously shared now is not shared.  When I go to share it again I get error "This Folder cannot be shared".  

Were running Windows 2008 R2 with two file servers clustered together.

Hi,
This problem is regarding Terminal Server connectivity (Remote Desktop Connectivity as per window server 2008). We have
following working scenario :

Architecture : Client-Server
Server : Dell T430 PowerEdge
Server OS : Windows Server 2008 R2(Standard Edition)
Terminals : Wyse S10 thin clients firmware version 6.1.0_08, 6.5.0_22 and 6.5.0_40

Recently we've shifted to a new server DELL PowerEdge T430 from DELL PowerEdge 2900. The thin clients used to connect

successfully to the old one. After the shifting process, the thin clients worked fine for about 1.5 months but suddenly today

afternoon they stopped connecting to the server all of a sudden.

Not able to figure out as to what exactly stopped the working terminals.

Thanks.