UCS B blade connection to terminal server

I have a UCS B200 m3. I would like to have console access from a termial server directly to the blade. Is there anything that I need to enable on the ucs manager?
I can go into the ucs manager and click on "KVM Console" and get a session, but I need to have it through the term server.
To try to accomplish this, I used the console port on the blade. It comes with a dongle that connects there. That dongle has a serial, 2 usb and a video port.
I connected the serial end to a serial cable, and with a ethernet connector (those small square ones) to one end of an octal cable on my terminal server.
I'm not getting anything on the console through the term server.
In the ucs manager I've tried going into the servers->Policies->root->BIOS defaults->Cisco UCS B200-M3->Server Management
There I've enabled console redirection and 9600BAUD
Also tried on
servers->Policies->root->BIOS Policies->SRIOV to change the console redirection fields. I had no progress with that.
Has someone done this before that can help? Or someone that has an idea how this should work?

Similar Messages

Can't connect to terminal server via Mac RDC

Users can't log in to our terminal server (Server 2008) from Mac using RDC 2.1. After typing in the server name, the client asks the user to login. The user fills in their username, password and domain but receives and error stating "The credentials
that were used to connect to [server_name} are incorrect".
Any user, including myself who am a Domain Admin, get this error. When I log in using the domain's Administrator account, however, I can log in just fine.
None of this occurs when trying to login from a Windows client. The Mac I tested on is running OS X 10.5.8. Any help would be greatly appreciated. Thanks.

Hi,
For remote desktop in MAC OS, you can try to update the new Remote Desktop Connection. New Multiple Session Support gives Mac users simultaneous access to multiple
Windows-based PCs or to a network server that hosts remote applications and files. Since it is a Universal application, Remote Desktop Connection Client 2 is compatible with the latest technologies on Windows and Mac platforms.
Please refer to the following link:
Microsoft Remote Desktop Connection Client for Mac 2.1.1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18140
Setting 'Allow connections from computers running any version of Remote Desktop (less secure)' in the Terminal server to sees if it’s work well.
Technology changes life……

Mac Client that can connect to Terminal Server Gateway

Anyone know of a Mac app that can connect to a remote computer via a Terminal Server Gateway? The Windows version of MS Remote Desktop will do this but of course that is Windoz only.

You could try CoRD. I don't know if it has the TS gateway option either, but it is an RDC client.
CoRD (Microsoft RDC Screen Sharing)
<http://www.macupdate.com/info.php/id/22770/cord>

Connecting to Terminal Server though RDP or CoRD?

I am running 10.9.1.
I have used RDP and CoRd successfully in the past prior to the latest OS upgrade. Neither program will connect to the terminal server and no one can connect to my Mac using TeamViewer or any other remote in.
Any ideas for troubleshooting?
Thank you,
Jeff

Peter--
Welcome to the Apple Discussions.
I actually don't know anything about this, but, like you, I'd expect you to need an application for the connection. Microsoft has a Remote Desktop Client for Mac that might well be what you're looking for. My guess would be that the .rdp file they gave you is probably the configuration for your network.
HTH,
charlie

RF's can't connecting to terminal server.

Hello,
I having trouble with my new terminal server. I am using RF's (intermec & motorola) in my business and We have two terminal servers that is running with 2008r2 standard. RF's can connect to first terminal server unproblematic but can't connect
to other one and getting error as "Because of a security error, the client could not connect to the remote computer, verify that you are logged on the
network, and then try connecting again"
I can connect to all terminal servers with my domain computer via remote desktop connection.
Own enterprise network has PEAP-WPA2 user authentication
Rf's are not in the domain.
I need help from you.
Thanks.

Hello everyone,
We found a solution regarding this case with microsoft team. Solution is in the following.
Issue Statement:
Cannot connect RF scanner to a particular server using RDP.
Symptoms:
> The RF scanners are Intermec CK3R devices with windows embedded handheld 6.5 classic installed on them. They fail to connect to
a particular server using RDP. However, same user and device can successfully connect to another server. The server to which the device fails to connect is TRKKTA01-N.
> Never been able to connect to the problem server.
> Both the good and the bad server are Windows 2008 R2.
> The Devices are connecting using per user licenses.
> We can connect to the problem server using a Fat client like Windows 7 machine with the same user ID.
> both the Problem server and the working server are in the same network but on different VLANs.
> On the Scanner, when trying to RDP user gets the following error:
"Because of a security error, the client could not connect to the remote computer, verify that you are logged on the network, and
then try connecting again"
> Already different encryptions have been tried but the connection still fails.
Environment:
RDS server is Windows 2008 R2. Clients are Intermec CK3R devices and OS is Windows embedded handheld 6.5 classic.
Scope Agreement:
We will close the case once we find the cause of the RDP failure and provide a possible fix for it.
If the problem is found to be due to third-party code we will provide information to substantiate this.
Case Status: Resolved.
Steps used to resolve the issue were:
1. Create the following reg key on the license server:
Use512LenPropCert on the Server
Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Registry entry: Use512LenPropCert
Data type: REG_DWORD
Value: 1
2. De-activate the license server
3. Re-activate the server using the telephone method
4. Delete the x509 cert keys from the terminal servers
Best Regards,
Ufuk BAYGIN

Entorno Terminal Sever / Terminal Server environment

Hola,
estamos migrando todas las aplicaciones delos usuarios de nuestra organización a un entorno de terminal server. Todas las aplicaciones residirán en el servidor.
Instalamos BDS en el servidor pero no logramos que funcione al conectar el dispositivo en el PC local a través de terminal server.
Utilizamos la versión 6.1 del cliente de escritorio remoto.
Se puede hacer o al estar el dispotivo conectado localmente no es posible realizar la sincronización?
Gracias.
Un saludo.
Jordi
Hi,
we are migrating all the applications of our users to a terminal server environment. All the applications will reside in the server.
We installed BDS in the server but when we connect the device in the local PC it doesn't work when we connect across terminal server.
We use rdp client 6.1.
We can do it or it is not possible?
Thanks in advance.
Regards.
Jordi

Hola,
estamos migrando todas las aplicaciones delos usuarios de nuestra organización a un entorno de terminal server. Todas las aplicaciones residirán en el servidor.
Instalamos BDS en el servidor pero no logramos que funcione al conectar el dispositivo en el PC local a través de terminal server.
Utilizamos la versión 6.1 del cliente de escritorio remoto.
Se puede hacer o al estar el dispotivo conectado localmente no es posible realizar la sincronización?
Gracias.
Un saludo.
Jordi
Hi,
we are migrating all the applications of our users to a terminal server environment. All the applications will reside in the server.
We installed BDS in the server but when we connect the device in the local PC it doesn't work when we connect across terminal server.
We use rdp client 6.1.
We can do it or it is not possible?
Thanks in advance.
Regards.
Jordi

SAP Connectivity slow - Terminal Services

Dear ALL,
we have two Locations (A & B) & Main Server is placed at Location (A) and users from Location (B) connect through terminal Server (IBM Server) there are approximatly 6 users who connect at a time to terminal server, so what should be the RAM size of the Terminal Server.
As of now we have given 2GB RAM, But the performance is very Poor
Applications:
SAP 2007B & 4 ADD-ons
Thanks in Advance

Hi Pankaj,
Check the following link
Sizing a Terminal Services server for Business One
Re: SAP BUSINESS ONE IS SLOW
Re: Slow SAP connection
SAP Business One Best-Practice System Setup and Sizing
*Close the thread if issue solved.
Regards
Jambulingam.P

Hyper-V could not replicate changes for virtual machine 'machinename': The connection with the server was terminated abnormally (0x00002EFE).

I have a 3 node cluster that has replica setup to replicate to another cluster off-site.
Suddenly one of the servers is not replicating with the error:
Hyper-V could not replicate changes for virtual machine 'machinename': The connection with the server was terminated abnormally (0x00002EFE). (Virtual Machine ID CC0FD4CC-F9B7-4C68-ABE8-B7D52A87899F)
All other servers are replicating fine so there cannot be a permissions or connectivity issue between the 2 clusters.
This server has 2TB of data so I'd rather not have to start the replication again.
Does anyone have any pointers?
Thanks.

Hi drensta,
Based on my knowledge , "hyper-v replica broker " is needed for failover cluster replica .
Here is a link for "Why is the "Hyper-V Replica Broker" required?"
http://blogs.technet.com/b/virtualization/archive/2012/03/27/why-is-the-quot-hyper-v-replica-broker-quot-required.aspx
Hope this hleps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How do I connect to a terminal server with my mac book pro

How do I connect to a terminal server with my mac book pro

Use the Remote Desktop icon on the tray and make sure to use the Fully Qualified Domain Name (FQDN) on the 'name of server' field. If that does not work then use the IP address to connect.

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

User gets "This network connection does not exist" when she tries to log on to Terminal Server (2008 R2)

User gets "This network connection does not exist" when she tryes to log on to Terminal Server (2008 R2)
I got more than 100 users. Shes the only one getting is. We tried four computers (All Windows 7 Pro)
Nothing useful in event viewer to mention.

Hi,
Thank you for posting in Windows Server Forum.
Does that user able to login previously?
From your comment, it seems that there is some permission issue with that user. As you have checked that user with different system also. Please check that user is added under “Remote Desktop User” local group and also allowed “Allow log on through
Remote Desktop service” permission under group policy. Also please check that when user tries to login it uses “Domainname\Username” format.
In addition for a try, also check by disabling firewall on one particular system.
To add users and groups to the Remote Desktop Users group by using Local Users and Groups snap-in:
1. Click Start > Administrative Tools, Open Computer Management.
2. In the console tree, click the Local Users and Groups node.
3. In the details pane, double-click the Groups folder.
4. Double-click Remote Desktop Users, and then click
Add.
5. In the Select Users dialog box, click Locations to specify the search location.
6. Click Object Types to specify the types of objects you want to search for.
7. Type the name you want to add in the Enter the object names to select (examples) box.
8. Click Check Names.
When the name is located, click OK.
More information:
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176/en-us
Hope it helps!
Thanks,
Dharmesh

SharePoint site connection with Office Professional Plus 2013 on Terminal Server

Hi,
Background info:
We use multiple Office 365 E3 subscriptions (12 now) and also have an Windows Server 2008 R2 Terminal Server.
The users may install Office 365 Pro Plus on their local machines and are able to connect to SharePoint online with the Office applications. Now not everyone has a PC so they log in to one of the two Windows Server 2008 R2 Terminal Servers. I do
however want one big happy family working with SharePoint so I installed Office Professional Plus 2013 and tweaked the Group Policies so that the start up screen and movie arent beeing showed.
When I log in with my test user on the Terminal Server (who has a E3 subscription) I miss the feature to add a location (to connect to the SharePoint site). I just do not have that feature. When I log in with my domain administrator account who also
has an E3 subscription, I am able to add a connection.
There is SO much info on the web about Office 365/Terminal Servers etc but I am not able to find what I was looking for.
Question:
What do I need to do so our Domain Users who log in to the Windows Server 2008 R2 Terminal Server are able to open/save files directly to the SharePoint site? How do I add the SharePoint location as shown in the image:

Hi,
SharePoint would not exist when Office 2013 initial installed. After you save a file to a SharePoint library for the first time, you can click
Save as you do for any file. Please try the following steps:
1) Add the document (Word file) to a document library on a SharePoint 2013 site
2) Click on the file within the SharePoint document library.
3) Click open in Excel
4) Save the file
5) Close Excel
6) Open Excel, select new Blank Workbook, File, Save As, "SharePoint" should now appear.
Regards,
George Zhao
TechNet Community Support

Word 2010 - "Connecting to printer" message when opening documents at Server 2008 R2 Terminal server

Our users experience sometimes the message "connecting to printer" while they open a document in Word 2010 (32-bit) on our Server 2008 R2 Terminal Server. This is behavior
isn't consequent but random. The default printer in this environment is a Net2Printer-printerdriver (1.16) which redirects the print jobs (in PDF-format) to the local client's default printer. This feature works well. We don't want to change the default printer
because this is the right one to use by our users.
After a long seeking trip on the internet I've found the Microsoft hotfix KB974991 which can fix this issue for Word 2007. My question is, is this also usable for Word
2010 (32-bit) and if not, is there maybe another fix for the 2010 version available?
Any other suggestions or workarounds are welcome!

Hi,
Please change following options test if it works:
Ÿ
Print proofs quickly
Enable the Draft output option. When you use this option, the document prints with minimal formatting. Therefore, the document
may print faster. This option is ideal for printing proofs.
To enable the Draft output option, follow these steps.
Note Some printers may not support this option.
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to select the Use draft quality check box, and then click OK.
Ÿ
Use the background printing option that best fits your requirements
When background printing is enabled, you can continue to work in Word while your document prints in the background. Background printing uses additional
memory, and your document may print more slowly.
When background printing is disabled, your document prints faster. However you cannot work in Word until the print job is completed. If you do not have
to continue to work in Word while your document prints, disable background printing to speed up printing.
To do this, follow these steps:
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to clear the Print in background check box, and then click OK.
Best regards
William Zhou
TechNet Community Support

Adobe Connect Add-in problems on terminal server

Windows 2003 Terminal server, IE7 and Flash version 10,0,12,36 using the Adobe hosted service
Were having problems with the add-in prompting to install though it has been. The add-in was “pre-installed” using the standalone package from the console as an Administrator.
The problem is that having launched a meeting the Administrator can use the add-in, but all other users are prompted to download \ install the add-in (again). Attempting to download the add-in fails with “A download error occurred, try downloading again”. There are no related errors recorded in the event logs on the server.
I've made calls to numerous Adobe support tel #s in an attempt to get support, or at least some response. Other than giving me another number to call, no one seems interested .

Rob, it sounds like port 1935 is being blocked. Can you verify that that port is open?
Have you gone to the Test Your Computer page for your connect account. After the diagnostics run, choose to send and email and then click on the details... link to see the results of the test.
Here is a link to that page for our hosted account, if that makes it easier: http://realeyesconnect.adobeconnect.com/common/help/en/support/meeting_test.htm
If needed, Connect only requires FP 10.3 or newer. If it comes to it, an older version of the Flash Player can be tested.

WSA S160 Support for Terminal Servers (How are terminal server connections handled?)

We have a terminal server environment with a mixture of computers and laptops. Currently we have multiple proxy servers and would like to considate down to one. Our current solution does not work well in a terminal server environment. We are looking for a way to integrate all equipment with one soluton and I was curious as to how the S160 handled users connecting via a terminal server.

Edadios thanks for the response. I was reading over this document (see attached), and it looks to me like the connection would be tracked via a cookie surrogate. My bigger concern is that we are looking to be able to track usage per user even though they are on a terminal server. Our current solution (Barracuda) is not able to perform this function. I am hoping to have a S160 on site this week to do some testing but was hoping to gather some intel in the forums prior to implementation.
The response helps clear up what protocols are in use but I am still wondering how terminal server connections are handled by the WSA and if they are truly handled and tracked per user instead of by the device they are connecing to.

UCS B blade connection to terminal server

Similar Messages

Maybe you are looking for