DNS server machine currently has no DNS domain name

DNS server machine currently has no DNS domain name

DNS server machine currently has no DNS domain name

This was a domain controller whose records in DNS were showing only the hostname name of the DC/DNS server. The records in DNS did not show the full internal FQDN. For example, the server name was only displayed, not server.domain.local . Computer group policies would not apply to member computers in the domain. Event ID 414 was being logged on to the DNS event log.

The server was a Windows 2008 R2 domain controller with integrated DNS role.  Although this problem is more prevalent with Windows 2003 domain controllers DBNSserver, in this case there is another domain controller on the network to which this server was joined to and promoted to a DC. That other server is a Windows 2003 Windows server.

This was fixed with a simple registry modification that did not even require a reboot. This 100 percent worked for me. Please read here for the steps and details.

Internet Explorer Welcome to your Browser, Meet your new browser pop-up on Citrix or RDS

Use group policy, local or domain, to prevent or stop the first run customization for Internet explorer 8  and higher.

Use group policy, local or domain, to prevent or stop the first run customization for Internet explorer 8  and higher.

Choices for users are Next or Ask Me Later

Welcome to Internet Explorer 8

Meet your new browser Internet Explorer 9

Enabled to prevent fisrt time use of internet explorer from pop-up when a user logs in. This takes affect for a stand alone system or for a RDS server with or without Citrix.  In this case Citrix xenapp 6.5 has been installed. 

Citrix Xenapp 6 and Xenapp Fundamentals -Terminal Server Listener Stack Was Down. System Cannot Find the File Specified.

xenapp fundamentals windows 2008 r2

Xenapp Fundamentals – Citrix Xenapp – Windows 2008 RDS (Terminal Server)

The relevant status code was: System cannot find the file specified. Terminal Server listener stack was down.

I did not find this solution in any of the documentation and although I had called in for support from Citrix, this was not unfortunately one of the things they looked for while trying to determine the cause of the error. I’m sure others will find this useful even if they are not useing Citrix Xenapp. This was a Microsoft problem, not a Citrix Xenpp problem.

 Event ID 1035

After checking with event viewer the system log and the application log, the following error was entered at the time of the installation failure.

Terminal Server listener stack was down. The relevant status code was: System cannot find the file specified .  Event ID 1035

Citrix Xenapp 6, Xenapp 6 Fundamentals 2008 R2 RDS

This occured during the installation of Citrix Xenapp Fundamentals on Windows 2008 R2. This error was preventign the applciation from istalling. This error can occur on a serve rthat does not have xenapp installed or during the install of xenapp. As this error is purely a terminal server Microsoft RDS issue. So users of RDS on 2008 R2 who experience this issue can try the solution used for a Citrix Xenapp install.

Terminal Server listener stack was down

This was an installation of Xenapp Fundamentals editions on Windows 2008 R2 server. Xenapp would not install on Windows 2008 R2 RDS (Terminal Server) .

For those of you who perhaps only have an RDS installation that is giving you this error message the solution does not change form those of you who may be experiencing xenapp installation issues due to the “Terminal Server listener stack is down” error.

Terminal Server Listener Not Available

Windows 2008 R2 RDS: The final thing that I was able to do to get pas this error and finallly install Xenapp on Windows 2008 server was to add the Xenapp server into the Terminal Server group on the local server. The other thing I did, although it is asl onot required but if you have a large environement you may have already configurd it this way, is to define the license server and not use discovery. Listing the license server may not have contributed to the “stack down” error but it is on of the lat things that were chanegd prior to the installation finally completing.