Remote Desktop connection defaulting to local machine

I ran into this the other day and needed to set the localhost name to the default login.  So you do the following but put the computer name in the domain field.

 

Q: How do I enforce the domain name in the logon dialog box?
Last modified: January 18, 2008

A: By default, the value for Domain/Computer in the logon dialog box is taken from the last logon that was used on the console. You can override this and force the correct domain name in the login box i Terminal Services Configuration:

Start – Administrative tools – Terminal Services Configuration – right-click RDP-tcp connection –
Properties – Logon Settings – select “Always use the following information”

Leave the User name and Password fields blank and enter the domain name you would like as the default in the Domain field.
Also make sure that you check the box for “Always prompt for password”.

 

Source: Remote Desktop connection defaulting to local machine

2003 to 2012 no SYSVOL or NETLOGON Shares

Problem

Migrating from 2003 to 2012 r2 Domain Controllers and after doing DCPromo, there were no SYSVOL or NETLOGON Shares.  Looked at event viewer on both servers.  This is what I saw.

The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR.

Replica set name is : “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
Replica root path is : “c:\windows\sysvol\domain”
Replica root volume is : “\\.\C:”
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

Solution

Did some searching on Google and found this.  I have used Burflags before but never fully understood which is which.  I found that this for some reason clicked with me.  So here is it.

http://serverfault.com/questions/532192/no-burflags-in-registry

 

“burflags” was for FRS. Windows Server 2012 doesn’t have FRS, so the comparable procedure is described in this lengthy article:

How to force an authoritative/non-authoritative synchronization for DFSR-replicated SYSVOL (like “D4/D2” for FRS)

http://support.microsoft.com/kb/2218556

Note that there are two separate procedures, one for authoritative, the other for non-authoritative.

“You want to force the non-authoritative synchronization of SYSVOL on a domain controller. In the File Replication Service (FRS), this was controlled through the D2 and D4 data values for the Burflags registry values, but these values do not exist for the Distributed File System Replication (DFSR) service. You cannot use the DFS Management snap-in (Dfsmgmt.msc) or the Dfsradmin.exe command-line tool to achieve this. Unlike custom DFSR replicated folders, SYSVOL is intentionally protected from any editing through its management interfaces to prevent accidents.”

[…] the two procedures, like D2 (non-auth) or D4 (auth) …

“If setting the authoritative flag on one DC, you must non-authoritatively synchronize all other DCs in the domain. Otherwise you will see conflicts on DCs, originating from any DCs where you did not set auth/non-auth and restarted the DFSR service. For example, if all logon scripts were accidentally deleted and a manual copy of them was placed back on the PDC Emulator role holder, making that server authoritative and all other servers non-authoritative would guarantee success and prevent conflicts.

If making any DC authoritative, the PDC Emulator as authoritative is preferable, since its SYSVOL contents are usually most up to date.

The use of the authoritative flag is only necessary if you need to force synchronization of all DCs. If only repairing one DC, simply make it non-authoritative and do not touch other servers.

This article is designed with a 2-DC environment in mind, for simplicity of description. If you had more than one affected DC, expand the steps to include ALL of those as well. It also assumes you have the ability to restore data that was deleted, overwritten, damaged, etc. previously if this is a disaster recovery scenario on all DCs in the domain.”

 

For me I ended up doing this:

I Ran D4 on the 2003 box after running repadmin and it was showing no errors.  After I restarting the service all seemed to be working just fine.  Now I see SYSVOL and NETLOGON shares on the 2012 Server.

I see this on 2003 Event Viewer:

The File Replication Service successfully added the connections shown below to the replica set:
“DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”

“server.domain.local”
“server.domain.local”

and

The File Replication Service is no longer preventing the computer “server” from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.

 

How to truly disable UAC on Server 2012

Just ran into this with an admin account having UAC issues …

 

The fix:

“Deactivating UAC in Windows 2008 R2 was possible via running msconfig (for example winkey+r -> msconfig), going to the Tools tab and launching “Change UAC settings”. There, you select “Never notify” to disable UAC.

The same approach is still available in Windows Server 2012, though UAC is still active after you selected “Never notify”.
 You have the option to turn off UAC via registry by changing the DWORD “EnableLUA” from 1 to 0 in “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”

 

You will get a notification that a reboot is required. After the reboot, UAC is disabled.”

Why is Java on vCenter using most of the Memory? and How to fix it

So after installing a new 2008 R2 vCenter 5.5 I look at the memory usage and found it was using 88% of the memory.  I open up task manager and find Java running with 7 processes using as high as 1.2GBs of memory.  So like always I did a google search and found this vmware article.

Why?Configuring Tomcat server settings in VMware vCenter Server 5.1 and 5.5 (2021302)

Purpose

This article provides information on configuring Tomcat server settings in vCenter Server 5.1 and 5.5.Note: This is a not a comprehensive guide. For more information, see the vSphere 5.x documentation. If there is a discrepancy between the documentation and this article, assume that the documentation is correct.

Resolution

Starting with vCenter Server 5.1, VMware Tomcat Server settings can no longer be configured through the Windows user interface at Start > Programs > VMware > VMware Tomcat.vCenter Server 5.1 uses VMware vFabric tc Server, an enterprise version of Apache Tomcat 7. Unlike Tomcat version 6, which is used with earlier versions of vCenter Server, Tomcat version 7 does not provide a control panel in the Windows user interface. Instead, you configure Tomcat by editing configuration files manually.You can adjust the JVM maximum heap size for vCenter Server, vCenter Single Sign-On, vCenter Inventory Service, and Profile-Driven Storage Service.

This table provides the JVM heap size recommendations:

vCenter Server 5.1:

vCenter Server Inventory VMware VirtualCenter Management Webservices (tc Server) Inventory Service Profile-Driven Storage Service
Small inventory (1-100 hosts or 1-1000 virtual machines) 1 GB 3 GB 512 MB
Medium inventory (100-400 hosts or 1000-4000 virtual machines) 2 GB 6 GB 1 GB
Large inventory (More than 400 hosts or 4000 virtual machines) 3 GB 12 GB 2 GB

vCenter Server 5.5:

vCenter Server Inventory VMware VirtualCenter Management Webservices (tc Server) Inventory Service Profile-Driven Storage Service
Small inventory (1-100 hosts or 1-1000 virtual machines) 512 MB 3 GB 1 GB
Medium inventory (100-400 hosts or 1000-4000 virtual machines) 512 MB 6 GB 2 GB
Large inventory (More than 400 hosts or 4000 virtual machines) 1024 MB 12 GB 4 GB

Note:After adjusting the JVM heap size in the wrapper.conf file, VMware recommends restarting the VirtualCenter Management Web services. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Java setting options and file locations for vSphere services

  • VirtualCenter Management WebServicesConfiguration file location:installation_directory\VMware\Infrastructure\tomcat\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Single Sign-On (vSphere 5.1)Configuration file location:installation_directory\VMware\Infrastructure\SSOServer\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Single Sign-On (vSphere 5.5)Configuration file location:installation_directory\ProgramData\VMware\CIS\runtime\VMwareSTS\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Inventory ServiceConfiguration file location:installation_directory\VMware\Infrastructure\Inventory Service\conf\wrapper.conf

    Heap size parameter:

    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=heap_size

  • vSphere Profile-Driven StorageConfiguration file location:installation_directory\VMware\Infrastructure\Profile-Driven Storage\conf\wrapper.conf

    Heap size parameter:

    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=heap_size

  • vSphere Web ClientConfiguration file location:installation_directory\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf

    Heap size parameter:

    ########
    # JVM Memory
    ########
    wrapper.java.maxmemory=heap_size

  • VMware Log BrowserConfiguration file location:installation_directory\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\conf\wrapper.conf

    Heap size parameter:

    ########
    # JVM Memory
    ########
    wrapper.java.maxmemory=heap_size

For more information, see the Configuring VMware Tomcat Server Settings in vCenter Server section in the vSphere Installation and Setup guide and vSphere 5.5 Documentation Center