Month: November 2018

Situation: When upgrading Windows Server 2016 in a Windows 2012 R2 domain Controller, you may receive this message:

Active Directory on this domain controller does not contain Windows Server 2-16 ADOREP /FORESTPREP update

Resolution: Load Windows Server 2016 DVD. run these two commands on \support\adprep folder: Adprep /forestprep and Adprep /domainprep

D:\support\adprep>Adprep /forestprep

ADPREP WARNING:

Before running adprep, all Windows Active Directory Domain Controllers in the fo
rest must run Windows Server 2003 or later.

You are about to upgrade the schema for the Active Directory forest named ‘test.
local’, using the Active Directory domain controller (schema master) ‘TestSvr.te
st.local’.
This operation cannot be reversed after it completes.

[User Action]
If all domain controllers in the forest run Windows Server 2003 or later and you
want to upgrade the schema, confirm by typing ‘C’ and then press ENTER to conti
nue. Otherwise, type any other key and press ENTER to quit.

c

Current Schema Version is 69

Upgrading schema to version 87

Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch70.ldf”
Loading entries……
5 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch71.ldf”
Loading entries……..
12 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch72.ldf”
Loading entries……
17 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch73.ldf”
Loading entries……
22 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch74.ldf”
Loading entries……………
36 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch75.ldf”
Loading entries…….
42 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch76.ldf”
Loading entries……….
51 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch77.ldf”
Loading entries………….
63 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch78.ldf”
Loading entries……..
70 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch79.ldf”
Loading entries….
73 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch80.ldf”
Loading entries……..
80 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch81.ldf”
Loading entries…..
84 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch82.ldf”
Loading entries……..
91 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch83.ldf”
Loading entries……
96 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch84.ldf”
Loading entries……..
103 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch85.ldf”
Loading entries…….
109 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch86.ldf”
Loading entries……
114 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch87.ldf”
Loading entries……….
123 entries modified successfully.

The command has completed successfully
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\PAS.ldf”
Loading entries………………..
142 entries modified successfully.

The command has completed successfully
Adprep successfully updated the forest-wide information.

D:\support\adprep>Adprep /domainprep
Adprep successfully updated the domain-wide information.

D:\support\adprep>

Situation: The client is use Microsoft azure AadSyncService. They get this warning: The Health Agent(s) running on one or more servers is not connected to the Health Service and the Health Service is not receiving the latest data from this server. The last data processed by the Health Service is older than 2 Hours.

Troubleshooting:

Ensure that the health agents have outbound connectivity to the following service end points. It is possible that your firewall rules are blocking this connectivity.

1. *.servicebus.windows.net(Port 5671)
2. https://*.blob.core.windows.net
3. https://*.queue.core.windows.net
4. https://*.adhybridhealth.azure.com/
5. https://*.table.core.windows.net/
6. https://policykeyservice.dc.ad.msft.net/
7. https://login.windows.net
8. https://login.microsoftonline.com
9. https://secure.aadcdn.microsoftonline-p.com

If you use HTTP Proxy servers for outbound traffic, you can configure Azure AD Connect Health agents to use HTTP Proxy settings.

If outbound connectivity is not blocked, restart the following services on each server:

1. Azure AD Connect Health Sync Monitoring Service
2. Azure AD Connect Health Sync Insights Service

 

Situation: The user has a new computer with Windows 10 and Office 365. Now, she can’t combine files into PDF using Acrobat 9.

Troubleshooting: Based on our research,  Acrobat 9 doesn’t support Office 365 merge.

Situation: When the user tried to combine two Excel files into PDF, “Adobe Acrobat has encountered and unidentified error”.

Troubleshooting: 1. Install the Adobe Acrobat update or install latest version.

2. Make sure you r Acrobat license is activated.

3. Repair Installation.

4. I’m running into a similar problem and believe I have narrowed it down to the length of the file path.  It is not maxing out the OS file path length.  193 character file path will bomb, yet a file in the same location very similar file name except slight shorter, approximately 160 characters, will load combine without error.

 

Situation: The user received a password protected PDF file. She can’t print because of the Print is grayed out.

Troubleshooting: She need to go to security, enter the password. After that, she should be able to print.

Situation: the client use Windows backup tp backup their windows 2008 R2 server. It failed with this message: has failed with I/O.

Troubleshooting: it could be the bad USB drive. To test, use different USB drive.

Situation: After modifying registry in a windows server 2008 R2, we can’t login Windows. The keyboard doesn’t work and we don’t have login screen. It is freezing. We have tried Safe mode, but that doesn’t work.

Troubleshooting: We have following this article

How to recover a Windows system that does not start because of corruption in the registry http://www.howtonetworking.com/winissues/recoverwin1.htm

to copy registry files from c:\windows\system32\repair. However, it doesn’t have repair folder.

After searching for system, default, sam and security files, we find them under c:\windows\system32\config\regbackup. Copying latest those files into c:\windows\system32\config fixes the problem and we can login the windows.

Situation: the client use Windows backup tp backup their windows 2008 R2 server. It failed with this message: has failed with following error code ‘2155347997’. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.”

Troubleshooting: We fix this problem by making sure the Volume Shadow Copy is running.

Situation: The client tries to install Canon printer in Windows 10. He gets “failed”.

troubleshooting: install the printer driver first or run printer software.

Situation: We have enabled OneDrive Anyone share in Office 365. However, when users go to Onedrive to share, the Anyone is grayed out.

Troubleshooting: 1. Login Office 365>Admin>OneDrive>Share, check the Shareable: Anyone with link.

 

2. If that doesn’t fix the problem, In the same page: Admin>OneDrive>Share, make sure External share bar is in the top.

3. If you can set SharePoint Most permissive to top bar, Anyone, but not OneDrive, you may need to check the SharePoint share settings as shown below.