Find out if your domain SYSVOL replication is run by FRS or DFS-R


To be sure, run following command on one of your DCs:

dfsrmig /getmigrationstate

If response is “Start” it means you are using FRS
If response is “Eliminated” it means you are using DFS-R

The response indicates the state of FRS to DFS-R migration process. Following states are possible:

0 – “START”
1 – “PREPARED”
2 – “REDIRECTED”
3 – “ELIMINATED”

Windows Server 2008 and later

Advertisements

DisconnectSession


Server will get new up gradation 2016 OS


Prerequisite:

Need to take application level backup

PHASE-I :- Upgrade Windows Server 2008 R2 To SP1

Step:1

1) Login to the server 200.200.200.2

2) Navigate to the path C:\service pack\Windows Server 2008R2 SP1-KB976932-*64.
3) Click on the package and run as administrator.
4) Follow the steps to complete the installation and finish.
5) Take the reboot of the server and check the service pack installation status post reboot.

Step:2

“Follow the steps if SP1 fail to install
1) Login to the server 200.200.200.2 Take pre-reboot.
3) Go to the setup folder location Systemreadiness tool
4)Run the setup file.
5)Take a reboot
6) Verfiy the checksur.log file in the path %SYSTEMROOT%\Logs\CBS\CheckSUR.log
7) If any errors or warnings in logfile, open the link https://support.microsoft.com/en-in/kb/947821 go to the section How to fix errors that are found in the CheckSUR.log and follow the steps
8) Post fixing the errors, rerun the tool and check log file, it should not have any errors
9) Try installing SP1 again.

“Follow the steps if SP1 fail to install evenafter resolving the checksur.log errors

1)Contact SD team for log a call to SOC team to uninstall Antivirus on the server.
2)Post uninstallation, take prereboot
3)Try installing SP1 again
4) Post SP1 installation install the antivirus”

PHASE-II :- Upgrade Windows Server 2008 R2 SP1 To Windows Server 2012

1.Login to server: 200.200.200.2
2.Insert the windows server 2012 DVD into the DVD-ROM and click on Run Setup.exe.
3.On the Windows Setup screen, click on Install now.
4.We can also do a windows update once the upgrade is completed, so select No, Thanks.
5.Enter your product key for windows server 2012 and click on Next.
6.select the second installation mode, Windows Server 2012 Standard Edition (Server with a GUI). Click on Next.
7.Select Upgrade: Install Windows and Keep files, settings and applications. This will keep existing files, settings and applications and upgrade our server to windows 2012
8.The upgrade will take close to 20 minutes. Sit back and relax until the upgrade is complete.
Note:-Click on Server Manager, Click on Local Server, check the properties of server. We see that the operating system version is Microsoft Windows Server 2012 Standard.The upgrade process has been completed successfully.

PHASE-III :- Upgrade Windows Server 2012 R2 To Windows Server 2016

1.Login to server: 200.200.200.2
2.Insert the windows server 2016 DVD into the DVD-ROM and click on Run Setup.exe.
3.On the Windows Setup screen, click on Install now.
4.When that completes you will be direct to Get more updates. Here we have two options, you need to select one them, I have selected Download and install updates. Microsoft also recommends this option rather than the second one
5. After that in Select image window, select the operating system version standard, a Core or GUI (Graphic User Interface) version.
6.In Applicable notices and license terms select window accept the license and agreement by click Accept.
7.After selecting Nothing in the last step, a popup window will appear for confirmation. It will ask you Do you want to continue using this selection. Select “Yes” and go on.
8.When you reach to Ready to install window click Install to install the server 2016 on server 2012 r2.
9.Wait for some minutes and you will be direct to Installing Windows Server 2016. During this Process your computer will restart several times.
10.After several times restarts, you will be direct to Hi there page. Select your country, Language.
11.Select the license agreement by clicking accept.
12.Enter your Password and go on.

Windows Server Backup


This command line performs the following:

  • start backup – tells wbadmin.exe to start a backup
  • -backupTarget – this is the target volume to store the backup on, in this case F: (no trailing backslash)
  • -include – these are the volumes to include in the backup job, in this case D: and E: because they are the volumes with Exchange databases and transaction logs on them
  • -allCritical – this tells Windows Server Backup to also include any other volumes or data that are required for a full server recovery, eg the System volume and SystemState. This is optional if you only want to backup the Exchange data.
  • -vssfull – this tells Windows Server Backup to perform a full VSS backup of Exchange and truncate the transaction logs
  • -quiet – runs the command silently with no visual interaction

Windows server booting issue


First, I would like to confirm that if it is able to boot the computer as normal after launched repair.

 If the system cannot boot up, you may try the following steps:

     Reset BIOS

  1.     Use the Last Known Good Configuration startup option
  2.     Boot the computer in Safe Mode
  3.     Reset the registry in WinRE

 Reset the registry

===================

Cd  c:\windows\system32\config

Ren  default  default.old

Ren  sam  sam.old

Ren  security  security.old

Ren  software  software.old

Ren  system  system.old

Copy  c:\windows\system32\config\regback\default.old  default

Copy  c:\windows\system32\config\regback\sam.old  sam

Copy  c:\windows\system32\config\regback\security.old  security

Copy  c:\windows\system32\config\regback\software.old  software

Copy  c:\windows\system32\config\regback\system.old  system

 

LDAP ADsPath


LDAP://HostName[:PortNumber][/DistinguishedName]
LDAP ADsPath example Description
LDAP: Bind to the root of the LDAP namespace.
LDAP://server01 Bind to a specific server.
LDAP://server01:390 Bind to a specific server using the specified port number.
LDAP://CN=Jeff Smith,CN=users,DC=fabrikam,DC=com Bind to a specific object.
LDAP://server01/CN=Jeff Smith,CN=users,DC=fabrikam,DC=com Bind to a specific object through a specific server.

Distinguished Names VS RDN


The LDAP API references an LDAP object by its distinguished name (DN). A DN is a sequence of relative distinguished names (RDN) connected by commas.

An RDN is an attribute with an associated value in the form attribute=value; normally expressed in a UTF-8 string format. The following table lists typical RDN attribute types.

String Attribute type
DC domainComponent
CN commonName
OU organizationalUnitName
O organizationName
STREET streetAddress
L localityName
ST stateOrProvinceName
C countryName
UID userid

 

The following are examples of distinguished names.

CN=Jeff Smith,OU=Sales,DC=Fabrikam,DC=COM
CN=Karen Berge,CN=admin,DC=corp,DC=Fabrikam,DC=COM
%d bloggers like this: