Showing posts with label Windows 2008 server. Show all posts
Showing posts with label Windows 2008 server. Show all posts

Thursday, January 11, 2018

Windows: How to check previous IP address details

Operating system

Windows 2008 Server/ Windows 7

Scenario

After replacing the motherboard, need to assign old IP configurations But unfortunately, customer is not aware of previous IP address details.

Solution

In this case, using registry we can find out previous IP address details. Windows Registry path should be specified below:


Open the registry editor and locate the interfaces path.

Current and previous IP address details will list under:

“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Prameters\Interfaces”


There is a chance of multiple interfaces when we installed VMware or any other related application

Monday, July 9, 2012

Server hanging at Applying Computer Settings stage of the logon process

Operating system

Windows server 2008,
Windows 7,
Windows Vista

Problem

When we start a computer it stops responding and appears to hang at the "Applying User Settings" or "Applying Computer Settings" stage of the logon process.



Solution


As per the Microsoft articles this issue typically occurs after install a server certificate and then configure Secure Sockets Layer (SSL) on the computer. For example, we install a SSL server certificate in Internet Information Services (IIS) 7.0 and then enable HTTPS on your website to use the certificate.


This issue occurs because of a deadlock in the Service Control Manager database. The Service Control Manager tries to start the HTTP.sys service and then puts a lock in place in the Service Control Manager database. Then, HTTP.sys makes a call that requires Cryptographic Services during startup. Then, a request is sent to start Cryptographic Services. However, a lock is already in place in the Service Control Manager database. Therefore, a deadlock occurs.


Method1


Microsoft released a Hot fix for this issue it is available from the below link
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2379016&kbln=en-us

Method 2


To resolve this issue, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys depend on crytosvc service to be started first.


Open the registry editor by typing the command regedit.exe with administrative privilges.


Locate and then click the following registry subkey:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP


On the Edit menu, point to New, and then click Multi-string Value. Type DependOnService, and then press ENTER. Modify the value by typing the CRYPTSVC, and then click OK. Exit Registry Editor.


Restart the computer.


Method 3:


Microsoft Fixit team released the fix
Microsoft Fix it 50564 for solving this issue.

Saturday, June 9, 2012

How to verify Global Catalog Server Readiness in Windows server 2008

          
Operating System

Windows server 2008, Windows Server 2003.
Scenario

After enabled the global catalog role on a domains controller, we might want to ensure that it is properly functioning as a global catalog server before clients and services start querying the global
catalog partition on this server.
 How To
When a global catalog server has satisfied replication requirements, the isGlobalCatalogReady rootDSE attribute is set to TRUE and the global catalog is ready to serve clients.
To perform the following procedures you must be a member of the Domain Users group.
To verify global catalog server readiness by using LDP, perform the following steps:
1. Log on to a domain controller.
2. Click Start, click Run, type LDP, and click OK.
3. On the Connection menu, select Connect.
4. In the Connect box, type the name of the server whose global catalog readiness want to verify, as shown in Figure below
  

5. In the Port box, if 389 is not showing, type 389.
6. If the Connectionless box is selected, clear it and then click OK.
7. In the details pane, verify that the isGlobalCatalogReady attribute has a value
 of TRUE, as shown in Figure below.
 
Verify Global Catalog Server Readiness by using NLTest

To verify global catalog server readiness by using NLTest, perform the following steps:
1. Log on to a domain controller.
2. Click Start, and click Command Prompt.
3. In the Command Prompt window, type the following command:
nltest /server:servername /dsgetdc:domainname
 (where servername is the domain controller you want to validate global catalog readiness and domainname is the name of the domain to which the domain controller belongs).
4. Verify that GC is listed under the Flags section of the results, as shown in below figure.
 

Configuring TS Web Access in windows 2008 server

                       
Operating System
Windows server 2008
How To
Windows Server 2008 Terminal Services bundled with a service called TS Web Access. TS Web Access service  enables users to access a web page running on the system hosting the Terminal Server to obtain a list of desktops and remote applications which are available for remote access.
Here is the step by step to configure the TS Web Access in windows 2008 server.
Open the server manager by selecting the start/Administrative Tools. Open Roles Tab. On right pane select Add roles. Select the Terminal Service Role from the list.
 
Select next and continue. On next page select the Terminal server and TS Web Access services. Click next and continue with the default settings. TS Web Access requires a number of other roles, like IIS web server role. Click on the Add Role Services to ensure that these services are also installed. Click the Next button to review information about the services being installed. Click next to review the IIS services being installed. Click Next once again to move to the confirmation screen and click on Install to initiate the installation.
 

After restart open the Browser and follow the link
        http://systemID/ts
where the systemID is the IP address or system name of the Terminal server. On successful connection the browser will prompt for the user and password credentials..




Once entered, the TS Web Access page will appear, listing any remote applications available for access on the local system.
 To configure applications such that they can be launched from the Windows Server 2008 TS Web Access page they must first be installed for use with Terminal Services and then configured as RemoteApps.
Start -> All Programs -> Terminal Services -> TS Remote App Manager or by running remoteprograms.msc in a Run dialog or command prompt. Once launched, the manager will appear as follows.


To configure an application as a RemoteApp, begin by clicking on the Add RemoteApp Programs link in the Actions panel located in the top right hand corner of the TS RemoteApp Manager screen. This will display the RemoteApp wizard containing a list of currently installed applications. One or more applications may be selected from the list before pressing the Next button.



It is essential that any RemoteApps be configured for access via TS Web Access. To ensure this is the case, select the appropriate application from the list and click on the Properties button to open the RemoteApp Properties dialog as shown below. Within this dialog, make sure that the RemoteApp is available through TS Web Access box is checked.
 
Click OK to close the RemoteApp Properties dialog and then click Next in the wizard to proceed to the Review Settings screen and Finish to complete the configuration. Upon completion the applications will be listed under RemoteApp Programs s shown below.
With the RemoteApp applications configured they will now appear on the TS Web Access page ready to be invoked by a remote user..
 
When launched, these applications will appear within their own windows on the client desktop just as if they are locally installed applications

Thursday, June 7, 2012


Install the Active Directory Schema Snap-In in windows 2008 server


Operating System 
   
                    
Windows 2008 server 32/64 bit
Solution
We need to manage the AD DS schema, which can include extending the schema, modifying existing attributes and classes.
To install the Active Directory Schema snap-in, perform the following steps:
1. Log on to a domain controller or a member computer.
2. Click Start, and click Command Prompt.
3. In the Command Prompt window, type the following command and press Enter:
                               regsvr32 schmmgmt.dll
4. You will receive a notification that schmmgmt.dll was registered successfully, as shown in Figure below. Click OK and close the Command Prompt window.


5. Click Start, click Run, type mmc /a, and click OK. On the File menu, click Add/Remove Snap-In.
6. In the Add or Remove Snap-ins window, select Active Directory Schema under Available Snap-ins, click Add, and then click OK. The Active Directory Schema snap-in is added to the MMC console, as shown in Figure below.



7. On the File menu, click Save As. In the Save As window, type %systemroot%\System32\schmmgmt.msc in the File name field, and click Save.

8. Close the console. Right-click Start, and click Open All Users. Double-click Programs double click Administrative Tools. On the File menu, click New; then click Shortcut.
9. In the Create Shortcut Wizard, the Type the Location of the Item box, type schmmgmt.msc; then click Next.

10. On the Select a Title for the Program page, in the Type a name for this shortcut,
type Active Directory Schema; then click Finish.

11. To verify that the Active Directory Schema shortcut was created successfully, click Start, click Administrative Tools, and verify that Active Directory Schema is listed, as shown in figure below
                          

Saturday, March 24, 2012

Managing Your Servers Remotely using the RSAT Tools

Enter the Remote Server Administration Toolkit (RSAT).
Unless you are using System Center to administer your servers, chances are you are either using PowerShell or, more likely at this point, MMC (Microsoft Management Console) consoles. As we learned in Microsoft Windows 2000 Server, MMC consoles can connect to remote servers (or desktops) as long as Windows Remote Management (WinRM) is enabled (Actually WinRM and the Windows Firewall were only introduced in Windows Server 2003 R2 if memory serves, but MMC consoles were remoteable 
You can enable WinRM in Windows Server 2008 R2 from the Server Manager main screen (as shown):
clip_image004
clip_image006
clip_image008
(Note: For those of you running Server Core installations… good for you! you can do all of this with a simple command line: WinRM /quickconfig)
Now that we can remotely manage our servers, we can do so from any Windows Server 2008 R2 box by adding the appropriate feature from the Add Feature Wizard:
clip_image010
I should mention that you will not be able to manage systems on which you do not have credentials, and although the RSAT tools can work in a workgroup, they are much more fluid and trouble-free in a domain environment. Also remember that adding the role or feature under RSAT does not install the actual role or feature, only the consoles required to manage them.
This is great for administrators who want to manage their servers remotely from another server… but what about managing them from your desktop? There’s a simple solution for that. Simply download the Remote Server Administration Tools (RSAT) for Windows 7 (http://www.microsoft.com/download/en/details.aspx?id=7887) from the Microsoft Download Center. Using another version of Windows? There is an RSAT download available for WIndows Vista, but if you are still running Windows XP then I am afraid you are out of luck (…and have 777 days until #EndOfDaysXP!).
Once you have downloaded and installed RSAT into your Windows 7 machine you will see no difference. However if you go to Turn Windows features on or off, things start to change. To get there, open Windows Explorerand navigate to Computer. If you do not see the option to Uninstall or change a program chances are you have not clicked on Computer.
clip_image012
You should see a list of your installed programs on the right, but to the left there should see an option ‘Turn Windows features on or off (shown). Click there.
clip_image014
clip_image016
It will take a couple of minutes, but when it is done you are ready to start administering your servers from Windows 7… just click on the Start pearl, expand Administrative Tools, and the new consoles should be there.
clip_image018
You can load any of them up (for this example we will use Hyper-V Manager) and you have… nothing. However you can right-click on Hyper-V Manager in the Navigation pane, and click Connect to Server…
clip_image020clip_image022
You can add multiple remote servers to the same MMC console (seen below), including full installations of Windows Server, as well as Server Core installations and (in the case of Hyper-V hosts) Windows Hyper-V Server, which have to be managed remotely as they have no graphical user interface (GUI).
clip_image024
Manage your servers from your desktop without ever having to leave your office/cubical/desk/cafeteria. Wherever you like to work from!

Friday, March 23, 2012

Manually sync the time of a client computer with the domain?




 You might need to manually synchronize the time of a client computer within a domain. Note that this need should be the exception rather than the rule; Windows 2000 (Win2K) and later


computers in a domain should automatically synchronize time with a domain controller.
Manually synchronizing the time will not resolve the underlying time sync issue, but might
temporarily resolve any other problems that arise from a lack of proper time sync (such as userand computer logon issues).


One common reason to manually synchronize a computer’s time is as a troubleshooting step. For example, if you notice System event log entries from the W32Time service, which indicate that time synchronization failed, you might attempt to manually sync the time as a troubleshooting step.
Typically, failed time synchronization is the result of the computer being unable to contact a domain controller, and you should troubleshoot that problem directly. Once the W32Time service fails to locate a domain controller, it will reduce its activity to location attempts every 16 hours until restarted. You’ll see
System event log messages to this effect, with Event ID 64, whenever the service is unable to locate a domain controller for a long period of time.


To manually synchronize time, open a command-line window, and run
net stop w32time
Run
w32time –update
Run
net start w32time
Manually verify the synchronization between the client computer and a domain controller. Also check the System event log to ensure that the W32Time service has not logged additional error messages.

Thursday, March 22, 2012

The Windows Firewall Service Fails to start


There can be several causes that will prevent the Windows Firewall from starting and I will attempt to cover them in this series of five blog posts. In this first post, I will cover Windows XP and Windows Vista / Windows 7 separately as they are two different services. Last I will cover one issue with OneCare. Note: Specifics on Windows Vista and Windows 7will come in a later blog post.

Windows XP

In Windows XP, the firewall service is named "Windows Firewall/Internet Connection Sharing (ICS)", or SharedAccess service.
Typical errors seen as either popups or within event logs when the service fails to start are:
  • Cannot start the Windows Firewall/Internet connection sharing (ICS) Service on local computer
  • Error 2: The system cannot find the file specified
  • Error 1705: While starting windows firewall and internet connection sharing services
Problems starting the Firewall Service in Windows XP are most commonly related to an issue with the Shared Access registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess
The quickest resolution is generally to rebuild the key. Instructions for doing this are in the following article, along with a FIXIT link:
Other things you will want to check are:
  • Verify that the "Remote Procedure Call (RPC)" service is started
  • Verify that the service is configured to logon as Local System Account, as shown below:
clip_image001
The above 3 items cover the vast majority of the issues with starting the Firewall in Windows XP.

Windows Vista and later (Windows 7, Windows Server 2008, and Windows Server 2008 R2)

In Windows Vista and later, the firewall service is "Windows Firewall" (MPSSVC); it combines both Firewall and IPsec functionality.
The first thing to check is that the Base Filtering engine (BFE) is running. There are a number of services dependent on the BFE service (including the Windows Firewall) that may also fail to start:
  • IPsec Policy Agent (PolicyAgent)
  • Windows Firewall
  • IKE and AuthIP IPsec Keying Modules
  • Internet Connection Sharing (ICS)
  • Routing and Remote Access
In my experience most of the issues starting these services are related to permissions.
Typical errors seen in relation to starting this service are:
  • Event ID: 7024 - The Windows Firewall service terminated with service-specific error 5 (0x5)
  • Windows could not start the Base Filtering Engine service on Local Computer. Error 5: Access is denied.
  • Windows could not start the IPsec Policy Agent service on Local Computer. Error 1068: The dependency service or group failed to start.
  • Windows could not start the Network Location Awareness on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -1073741288.
  • The Windows Firewall service terminated with service-specific error 87 (0x57)
  • Error 0x80004015: The class is configured to run as a security id different from the caller.
  • The Windows Firewall service terminated with service-specific error 6801 (0x1A91).
  • "net start mpssvc" in cmd.exe returns the system error 1297.
What to look for (specific details will be shared in a future blog post):
  • Verify Log On permissions
  • Verify registry permissions
  • Verify privilege permissions
  • Verify Service Dependencies
  • Reset the default security permissions
  • Verify that the TxR folder exists : %systemroot%\system32\config\TxR
  • Verify the following registry keys by comparing them to a default Windows installation:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BFE
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MpsSvc
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ShareAccess

Windows OneCare

Lastly, I am including information about one issue that may be seen with the Windows OneCare Firewall Service. The following messages may be seen:
The Windows OneCare Firewall Service Could not Start
Urgent - Turn on Firewall
You will see this error in the Windows OneCare interface, with a red status action item asking you to enable the firewall. The action listed does not enable the firewall, however.
This issue is also very specific because the firewall settings in Windows OneCare are grayed out and cannot be modified.
To resolve this issue:
Use the steps below to ensure that the PATH environment variable contains the following path:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM
  1. Click Start / Control Panel and open the System Icon.
  2. In System, click the Advanced tab and then Environment Variables.
  3. Ensure that in the lower box "System variables" that PATH exists. If Path does not exist click NEW and type in PATH as the variable name and enter the above path in the variable value.
  4. If PATH already exists, highlight it and click Edit.
  5. Under variable name, click at the end of the line to append the above mentioned path to the end of the current path. NOTE: BE SURE TO SEPERATE THE OLD PATH AND THE NEW PATH WITH A SEMI-COLON ( ; ).
  6. Click OK to close the windows and restart the computer.
If this does not resolve the issue, try the following step:
  1. Click Start / Run and type Regsvr32 %SystemRoot%\System32\wbem\wmidcprv.dll and click OK.
  2. Restart the computer and test the firewall again.
If this does not resolve the issue, or if the problem does not match the description, please follow the steps in KB article 910659.

Error message when you try to perform a system state backup in Windows Server 2008 and Windows Server 2008 R2


When you try to perform a system state backup to a volume on which the system state file resides, you receive an error, as mentioned below:


In Windows Server 2008, you receive the following error:
ERROR - The location for backup is a critical volume.


In Windows Server 2008 R2, you receive the following error:
ERROR - The backup storage location is invalid. You cannot use a volume that is included in the backup as a storage location


This behavior occurs because system state backups to critical volumes are blocked in 
Windows Server 2008 and Windows Server 2008 R2.


You can change the default behavior of Windows Server 2008 and Windows Server 2008 R2 by adding a registry entry. You must also verify that the following prerequisites are met before you perform a system state backup to a critical volume.



Prerequisites to perform system state backups to critical volumes


Make sure that the target volume has no shadow copy before the backup starts.


If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.


Periodically check that no other user or program maintains a shadow copy on the target 
volume.


Do not keep volume level backups and system state backups in the same location.


The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes.




Notes


Any writes on target volume with shadow copies will increase the diff area size. 


If the diff area is bounded, it may cause deletion of shadow copies.




Incremental backups leaves shadow copies behind, it will cause side effect as point 1.


Backup stores different versions as shadow copies, it will cause side effect as point 1.



Registry entry to enable system state backups to critical volumes




To enable the system state backup files to be targeted to critical volumes, you must set the


 value of the AllowSSBToAnyVolume registry entry under the following registry subkey:




HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\


Set the value of this entry as follows:


Name: AllowSSBToAnyVolume


Data type: DWORD


Value data: 1


Note When this value is set to 1, system state backups to any volume are enabled. To revert


 to the default behavior, set the value to 0.





Wednesday, January 25, 2012

Bootmgr is missing error in windows 7



Bootmgr is missing error in windows 7
Release

Windows 7

Problem

While booting in to windows 7 showing the error “bootmgr is missing. Press Ctrl+Alt+Del to restart”.

Solution

Method 1:

1.     Please insert the Windows 7 DVD media and restart the computer.
2.     Choose your language settings, and then click "Next" option.
3.     Select the option "Repair your computer".
4.     Select the operating system you want to repair, and then click "Next".
5.    On the System Recovery Options screen, select the option "Startup Repair". Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

Method 2:
1.     Please insert the Windows 7 DVD media and restart the computer
2.     Select the option "Repair computer".
3.     Select "Cancel" to exit the repair wizard.
4.     Select "command prompt" option from the available options
5.     Type your "DVD-DRIVE LETTER" in command prompt, press ENTER.
6.     Let us assume windows 7 is installed in C drive, type "copy bootmgr c:\" without codes, press ENTER.
7.    Type "exit", press ENTER.
8.     Restart computer.
9.  Select "start windows normally".

Method 3:

1. Please insert the Windows 7 DVD media and restart the computer.
2. Choose your language settings, and then click "Next" option.
3. Select the option "Repair your computer".
4. Select the operating system you want to repair, and then click "Next".
5. In the System Recovery Options dialog box, select Command Prompt.
6. Type Bootrec /RebuildBcd , and then press ENTER.
7.Restart the computer
  

Mapped Drive Connection to Network Share May Be Lost


Mapped Drive Connection to Network Share May Be Lost

Release
Windows 7,Windows 2008 server enterprise

Problem
 The mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red "X" on the icon of the mapped drive. However, if you try to access or browse the mapped drive, it reconnects quickly.

Solution
This behavior occurs because the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. The connection can be re-established very quickly, if required.

Method1:

1.Open registry editor and locate the following path
  
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
 2. In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:
        On the Edit menu, point to New, and then click REG_DWORD.
        Type autodisconnect, and then press ENTER.
        On the Edit menu, click Modify.
         Click Hexadecimal.
   3. In the Value data box, type ffffffff, and then click OK. Close the registry editor and restart the PC


-----------------------------------------------------------------------------------------------------------------------

Procedure to clearing the ConfigMgr (SCCM) client local cache (CCM cache) -Resolving Disk space isssue

Essentially the client cache is a temporary download location for software, applications and software updates that are deployed to a clie...