Author: Bob Lin

Situation: The client find their WSUS server is out spaces.

Here are some suggestions to free spaces.

1. Make sure Update Files and Languages is configured to only download updates in languages which you support. To do that, open ASUS Console, go to Options>Update Files and Languages>Update Languages, make sure only check English in our case.

2. You may want to run ASUS Server Clearnup Wizard. To do that, go to ASUS Console>Options>ASUS Server Clearnup Wizard, follow the wizard to clean up.

3. Do not store update files locally

Go to Options>Update Files and Languages, check Do not store update files locally,.

4. Clean up WSUS by running the following commands:

net stop wsusservice

cd “C:\Program Files\Update Services\Tools”

wsusutil.exe reset

echo Delete WSUS Folder Content

pause

net start wsusservice

1. Access EDIMAX AP by opening a web browser and entering the access point’s default IP address “http://192.168.2.1” into the URL bar.
2. default username is admin and the default password is 1234.
3. Follow the wizard to setup AP.
4. Configure AP Mode: There are 6 AP mode. They are:

1) Select “Basic Settings” from the menu on the left side of the screen.

2) Open the drop down menu labeled “Mode” and select one Mode from the 6 available modes:

AP
Station-Infrastructure
AP Bridge-Point to Point
AP Bridge-Point to Multi-Point
AP Bridge-WDS
Universal Repeater

This is the screenshot of Station-Infrastructure.

Note: It is recommend to use “Select Site Survey”.

Press the WPS/Reset Button and hold for 20 seconds to reset the access point to factory default settings.

Note: Press this button for less than 5 seconds to start WPS functions.

1. Go to Active Directory Domains and trusts.
2. Right click on it and select Properties.
3. You should see Domain and Forest function level info.

You can explicitly test connectivity between Azure AD Connect Health agent with the Health service by using the following command:

Test-AzureADConnectHealthConnectivity -Role Sync

EDIWAX WiFi AP default username and password: admin/1234

default IP: 192.168.2.1.

1. Login domain admin account in one of Domain controllers.
2. Open Active Directory Users and Computers by clicking Start > All Programs > Administrative Tools, and then click Active Directory Users and Computers.
3. Right-click the domain node and then click Raise Domain Functional Level

4. Under Select an available domain functional level, select domain function level.

5. When popup warning message, click Ok.

6. Click OK when you will receive an acknowledgement message telling you that the operation was completed successfully.

7. Go to Active Directory domains and trusts and right click on it. Select Raise Forest Function Level.

To check the domain and forest function level, please refer to this page:

• How to check Domain and Forest function level status

Q: What can be done prior to raise Windows function level?

A: Verify that Active Directory is replicating properly to all DCs. The Domain and Forest Functional Levels are essentially just attributes in Active Directory. The Domain Functional Level for all domains must be properly replicated before you’ll be able to raise the Forest Functional level. This practice also addresses the question of how long one should wait to raise the Forest Functional Level after you’ve raised the Domain Functional Level for all the domains in the forest. Well…what is your end-to-end replication latency? How long does it take a change to replicate to all the DCs in the forest?

Q: Which client and server OS are supported to join Windows domain?

A: Quoted from Microsoft article:

The following Windows client and Windows Server operating systems are supported for domain member computers with domain controllers that run Windows Server 2012 or later:

• Client operating systems: Windows 8.1, Windows 8, Windows 7, Windows Vista
  • Computers that run Windows 8.1 or Windows 8 are also able to join domains that have domain controllers that run earlier version of Windows Server, including Windows Server 2003 or later. In this case however, some Windows 8 features may require additional configuration or may not be available. For more information about those features and other recommendations for managing Windows 8 clients in downlevel domains, see Running Windows 8 member computers in Windows Server 2003 domains.
• Server operating systems: Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, Windows Server 2003

Q: Our Domain is Windows 2012 R2 wit 2003 function level. If we upgrade to Windows 2012 R2 function level, does that cause any problem on Windows 2008 servers?

A: That should be fine. Quote from Microsoft article:

Windows Server 2012 requires a Windows Server 2003 forest functional level. That is, before you can add a domain controller that runs Windows Server 2012 to an existing Active Directory forest, the forest functional level must be Windows Server 2003 or higher. This means that domain controllers that run Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 can operate in the same forest, but domain controllers that run Windows 2000 Server are not supported and will block installation of a domain controller that runs Windows Server 2012. If the forest contains domain controllers running Windows Server 2003 or later but the forest functional level is still Windows 2000, the installation is also blocked.