Unable to enable remote desktop (XDMCP) after jumpstart Solaris 10 U9

Hi,
I have installed Solaris 10 U9 using the jumpstart.
I would like to have enabled remote desktop (XDMCP) after installation.
But Solaris 10 U9 has this option disabled:
# ps -ef | grep dt
root 858 450 0 04:56:05 console 0:00 grep dt
root 730 1 0 04:41:39 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0
I have copied dt config files to /etc:
# mkdir /etc/dt/config
# cp -r /usr/dt/config/* /etc/dt/config/.
Then in /etc/dt/config/Xconfig I've uncommented and added port number:
Dtlogin.requestPort: 177
After reboot this change in Xconfig doesn't enable XDMCP.
Do you know what to change to have XDMCP enabled after jumpstart installation?
Thanks,
Daniel

By default xdmcp will start on udp port 0. normally it should listen on 177.
Try this. you should be able to login through xdmcp after this.
#svccfg -s cde-login setprop 'dtlogin/args=""'
#svcadm restart cde-login

Similar Messages

  • How do I enable remote desktop for my free trial of azure?

    I have a free trial with Azure, which I am trying to setup remote desktop access to.
    Following these instructions (http://azure.microsoft.com/en-us/documentation/articles/cloud-services-nodejs-enable-remote-desktop/) I see that I am to enable remote destop using the following cmdlets
    (under the project directory)> Enable-AzureServiceProjectRemoteDesktop 
    and then
    Publish-AzureServiceProject
    However the second step is asking me to specify the subscription:
    publish-azureserviceproject : No current subscription has been designated. Use **Select-AzureSubscription -Current <subscriptionName>** to set the current subscription.
    However, I don't know the name of my subscription. It is listed as Free Trial in the azure management portal, however the following command cannot find any such named subscription
    > Select-AzureSubscription -Current "FREE TRIAL"
    Message:
    Select-AzureSubscription : The subscription named 'FREE TRIAL' cannot be found. Use Set-AzureSubscription to initialize the subscription data.
    The error message also advises that I use the Set-AzureSubscription cmdlet, but again, I don't know what my subscription is named.
    > Set-AzureSubscription "Free Trial"
    Set-AzureSubscription : Cannot bind positional parameters because no names were given.
    Thanks for any help!

    hi James,
    you can either manually configure your Windows Azure Subscription with the Windows Azure PowerShell Cmdlets or you can use a publish settings file.
    Please follow this
    blog post by Michael Washam
    Hope this helps
    Please mark as answered if it helped
    Vishal Narayan Saxena http://twitter.com/vishalishere http://www.ogleogle.com/vishal/

  • Enable Remote Desktop Connections with PowerShell

    What is the easiest way to enable remote desktop connections on Windows 7, with powershell?

    Use Shay Levy's "Remote Registry PowerShell Module", and modify the value of the "fDenyTSConnection" value in the
    key "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" on the remote box to "0"
    The Windows 7 box will need to be rebooted before it will take effect.
    See http://oreilly.com/windows/archive/server-hacks-remote-desktop.html
    Or, grab Michal Gajda's script "Enable-RDP.ps1" in the gallery :)
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
    My Blog: http://unlockpowershell.wordpress.com
    My Book:
    Windows PowerShell 2.0 Bible
    My E-mail: -join ("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})

  • How enable remote desktop gateway manager server 2012 essentials

    how enable remote desktop gateway manager

    There is a DISM command,
    dism /online /disable-feature:Gateway-UI
    http://support.microsoft.com/kb/2472211/en-us
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Enabling remote desktop access to a simple windows 2012 datacenter edition server

    Hi,
    I am a complete noob to server administration. I installed a windows 2012 server initially as a workgroup. All i need is to enable a user to remotely access my server(using remote desktop). The firewall that I use is Gibraltar.
    I read that to enable remote desktop services my server has to be part of a domain. So i promoted my server to a domain name controller. Using active directoty I added a user to the domain. I also read that to make remote desktop more secure, I have to request
    the user to login through a VPN. 
    Now here is where I am completely lost. Do i really need to move my server to a domain, if the user just wants access to this server and nothing else? Should i restrict remote desktop access only through VPN
    and if so, how can i do that? Further, the server dashboard gives me notifications about 'remote desktop licensing' not configured. We got the software as a campus licensing and I am not sure how to configure the remote license server. Any opinions are highly
    appreciated.

    If you're just trying to setup this to allow administration access then I don't believe you need it to be a member of a domain. There's a difference between allowing remote desktop access for administration, and setting up full terminal services access for
    multiple users. The latter requires a lot more work and licensing unlike the former.
    To simply allow admin access, open an explorer window and right click on Computer, then select properties. In the System window that appears, click Remote settings on the left. Now in the bottom half of the window select "Allow remote connections to this
    computer" and leave the option requiring NLA in place. Click Select Users..., you'll see that the administrator user already has permissions to connect, so if you're only planning to connect with that then you're finished, otherwise find those users you
    want to grant access.

  • Qos DSCP value 46 gone, after enabling Remote Desktop Services on Windows 2012 R2 Standard

    Hi,
    After installing a clean Windows Server 2012 R2 with
    all Windows updates I have setup Policy-Based QoS for tagging defined traffic,
    in the test case all traffic to one specific ip address. Whireshark logging
    displays the correct configured (46) dscp value so the group policy is
    working fine. After installing Remote Desktop Services the Policy-Based QoS is
    still in place but Wireshark results that the value is 0.
    Can somebody explain why this happens and how to solve
    it?
    Regards, Edward

    Hi Edward,
    Thank you for posting in Windows Server Forum.
    Did you find any related error for your case?
    By default, Windows traffic has a DSCP value of 0. Network routers use the DSCP value to classify network packets and to queue them appropriately. The number of queues and their prioritization behavior needs to be designed as part of your organization's QoS
    strategy. For example, your organization may choose to have five queues: latency-sensitive traffic, control traffic, business critical traffic, best effort traffic, and bulk data transfer traffic.
    More information, please see:
    Policy-based Quality of Service (QoS)
    http://technet.microsoft.com/en-us/library/dd919203(v=ws.10).aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Unable to establish Remote Desktop Connection (RDC)

    Hi all,
    I had activated my account for Instance of SAP Business Warehouse 7.4 SP5 incl. SAP Business Objects BI 4.1 SP2 on SAP HANA 1.0 SP7 but while trying to connect using remote desktop connection, I am unable to connect. Its throwing up the error, "Remote desktop can't connect to the remote computer for one of these reasons". The screen shot of the error message is attached to this post.
    I am trying to connect to the servers 54.204.35.135 (SAP Frontend) and 54.225.249.36 (SAP Server). Both of them I am getting the same message.
    After I activate the instance on CAL, I see that on Amazon Cloud these instances are automatically started. Then I go to elastic IP and hit on associate these IPs to associate them.
    Please let me know if I need to do anything else.I am using a company laptop and am afraid if these IP addresses are being blocked somewhere.
    Please advise how to establilsh the RDC.
    Thank you.
    Regards,
    Pavan.

    Hi Pavan,
    the following comment in your initial question draw my attention:
    After I activate the instance on CAL, I see that on Amazon Cloud these instances are automatically started. Then I go to elastic IP and hit on associate these IPs to associate them.
    So you started the solution (that contains 2 images) in CAL and then changed some configuration settings in the EC2 web console, correct?
    It is important to understand, that changes to the configuration of the instances, that are made outside of CAL will have a severe impact. Only CAL knows how to configure both instances correctly, especially when it comes to the network and communication between each other.
    If you don't mind, would you be able to shutdown and terminate all running instances of this Trial solution in CAL and start from scratch without using the EC2 web console. We have throusands of users of this system and all of them get the same software - all works. I suspect the changes in the EC2 console to be a culprit here.
    All these activities should be done in CAL, not in the EC2 console:
    So please terminate all instances of this solution and wait until they are completely removed.
    Then go to the Solution tab and click on create instance
    go through the guided procedure and pay attention on the firewall / port settings in step 3
    finish and wait 30 minutes until the solution is fully started
    try to connect.
    Please let us know the result.
    Regards,
      Hannes

  • Remote Desktop Fail after March 10 Updates!

    I updated client servers with MS updates as usual over the weekend remotely. Tried to remotely log into 2 of the servers after they rebooted; Server 2008 R2 and 2008 Standard, and was denied with "Your credentials did not work" message at the top
    of the dialog. Administrator, other IDs did not work. Only way to log into either server was to drive into the client (on Sunday) and login from the console. Once logged in from the console I was able to RD into each. If the server is rebooted RD is again
    unavailable until logged in from the console. I am now seeing that remote access works for a while but in some cases becomes unavailable after a while. The problem only seems to affect server 2008 and 2012 variants.
    Backed out the following updates and the problem remained: KB3002657, KB3033929, KB3046049, KB3035131, KB3034344, KB3032359, KB3039066, KB3035132, KB3035126, KB3033889, KB3032323, KB3030377. Then I restored the System State from the day before the updates but
    the problem is still present.
    Unfortunately, this particular client has around 30 remote users who need to login every day. The only workaround I've found is to log their IDs in at the console first. Then they can connect remotely. Others have reported this problem and one post leads me
    to believe it could be an issue with 2008/2012 RDS boxes on a 2003 Domain Controller. Any help appreciated or, MS: Please Get This Fixed!
    More info:
    https://social.technet.microsoft.com/Forums/en-US/0a520543-29d4-4466-9967-e39d819d11f1/users-cannot-log-into-remote-desktop-after-3112015-update?forum=smallbusinessserver&prof=required

    We are both in the same boat.
    While it's nice to know that Microsoft gives us these broken updates so we can charge customers, there is that "loyalty" factor to our customers in which we end up absorbing the many hours of troubleshooting and research time spent.
    Failing to find a suitable solution to this problem by end of day I will attempt to remove ALL 27 Security Updates that were installed to see if this resolves the issue.
    What scares me is that you probably removed the applicable ones and that we will be in the same situation after removal.
    This thread seems a little more active:
    https://social.technet.microsoft.com/Forums/en-US/0a520543-29d4-4466-9967-e39d819d11f1/users-cannot-log-into-remote-desktop-after-3112015-update?forum=smallbusinessserver&prof=required

  • Remote desktop broken after 10.9.3 update

    After the 10.9.3 update, remote desktop is completely broken...
    The ard status monitor display : Apple Remote Desktop is disabled. I try a clean install (app + system library coreservice remote management + user library pref ans aap support deleted.
    After the Remote Desktop 3.7.2 installed from the Apple Store when i try to launch the application i get this message : The remote desktop client does not mach the administrator software version. Check for update.
    And this is the problem : there is no updates available !!!!
    I have try to install some 3.7.1 client from some dmg, but all false : ARD agent validate multiple error ( on log) error 6405, fatal error 5, error 100, error 6404, broken pipe, fatal error 0
    Now i am back to the clean uninstall and with the new Remote Desktop 3.7.2 with the desktop client not matching and not running...and without any update available.
    thanks for help !

    Nice idea and helping really !!!!
    On safe mode, i could install an old remote desktop client (3.6.x) - and the client works fine as client.
    Next i get the last Remote Desktop Admin from the Apple Store and it run also always in safe mode. No error, but all my setting were lost. With the Remote Desktop Admin running i created a new client installer and quit the Admin app for updating the client to the last release (3.7.1). I test all in safe mode (running as admin and as client) and finally reboot the computer to quit the safe mode.. and finally all was running again.
    I don't know why during the 10.9.3 update Remote Desktop was corrupted...
    Now i need to put back my remote client, but this not really a problem.
    Thank a lot th Deadzak for his genius intuition.

  • Enabling Remote Desktop On Windows 7 Home Premium

    So, I'm trying to set up a remote desktop connection on a computer. I already opened the ports necessary to do so (3389) and when I go to configure the remote settings through the system in control panel, Remote Desktop isn't there.
    I tried enabling it through editing the registry (even though I knew it wouldn't work) and tried numerous other things in efforts to get it working. No matter what I do, nothing seems to work in enabling the remote desktop options to show up like it does in the next picture.Anything to help get this remote desktop to work would be greatly appreciated.
    This topic first appeared in the Spiceworks Community

    follow this document for Windows 7 backup
    http://windows.microsoft.com/en-us/windows/back-up-programs-system-settings-files#1TC=windows-7
    how much space at target volume? external HDD? USB pen drive?
    i suggest using external HDD, USB pen drive will takes forever
    or you can also try using 3rd party application, but its our own risk and fully support comes from manufactured

  • Enabling Remote Desktop for Windows 7 as a task sequence

    Hi there.
    I have a task sequence to automate the creation of a base image of Windows 7 x64 Professional. In my base image I would like to have Remote Desktop enabled by default for all users. Is there a command or a script to do this that I can add into my task sequence to make this possible?
    Thanks.

    I have to agree except I can't understand why anyone would use anything other than the unattend.xml.  You can do all that plus so much more and it's the way Microsoft provides to do it.  This is my complete x64 unattend.xml version but I also have
    an x86 version.  This should give you some idea of it's capabilities.
    Drop the unattend.xml file into a package and reference it in the Task Sequence as shown below.  I dropped both my x86 and x64 version of the unattend.xml into the package.  I use an OSD HTA menu on the frontend to let helpdesk pick
    between x86 and x64.  I cropped the picture up a bit and took out company specific info but you should get the idea from the screen captures.  This is how I deploy x86 and x64 in a single task sequence. I mark every line with a condition in the task
    sequence with (C) which makes it easier to find lines with conditions.  I use the condition to assign x86 and x64 software among other things.  The selection in the HTA pretty much triggers everything.
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <settings pass="auditSystem">
       </settings>
       <settings pass="auditUser">
       </settings>
       <settings pass="generalize">
       </settings>
       <settings pass="offlineServicing">
       </settings>
       <settings pass="oobeSystem">
          <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
             <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <SkipMachineOOBE>false</SkipMachineOOBE>
                <SkipUserOOBE>false</SkipUserOOBE>
                <ProtectYourPC>3</ProtectYourPC>
             </OOBE>
             <UserAccounts>
                <DomainAccounts>
                   <DomainAccountList wcm:action="add">
                      <DomainAccount wcm:action="add">
                         <Name>Workstation Admins</Name>
                         <Group>Administrators</Group>
                      </DomainAccount>
                      <Domain>DOMAIN</Domain>
                   </DomainAccountList>
                </DomainAccounts>
             </UserAccounts>
          </component>
       </settings>
       <settings pass="specialize">
          <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <EnableLUA>false</EnableLUA>
          </component>
          <component name="Security-Malware-Windows-Defender" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
    http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance ">
             <DisableAntiSpyware>true</DisableAntiSpyware>
          </component>
          <component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <DisableSR>1</DisableSR>
          </component>
          <component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
             <PrivateProfile_EnableFirewall>true</PrivateProfile_EnableFirewall>
             <PublicProfile_EnableFirewall>true</PublicProfile_EnableFirewall>
          </component>
          <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
            <RunSynchronous>
              <RunSynchronousCommand wcm:action="add">
                <Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>
                <Description>Setting Network Location</Description>
                <Order>1</Order>
              </RunSynchronousCommand>
            </RunSynchronous>
          </component>
          <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <fDenyTSConnections>false</fDenyTSConnections>
          </component>
          <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <DisableAccelerators>true</DisableAccelerators>
             <DisableOOBAccelerators>true</DisableOOBAccelerators>
             <SuggestedSitesEnabled>false</SuggestedSitesEnabled>
             <DisableFirstRunWizard>true</DisableFirstRunWizard> 
             <DisableWelcomePage>true</DisableWelcomePage>
             <Home_Page>http://www.google.com</Home_Page>
             <SearchScopes>
                <Scope wcm:action="add">
                   <ScopeDefault>true</ScopeDefault>
                   <ScopeDisplayName>Google</ScopeDisplayName>
                   <ScopeKey>SearchProvider1</ScopeKey>
                   <ScopeUrl>http://www.google.com/search?q={searchTerms}</ScopeUrl>
                </Scope>
             </SearchScopes>
          </component>
          <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
            <TimeZone>Central Standard Time</TimeZone>
          </component>
       </settings>
    </unattend>

  • Since my Maverick infall, I'm unable to use remote desktop connection, What can I do?

    Since I updated to Maverick, i am unable to cconnct to my job's server through the remote desktop connection.  I know the problem is not at work since I'm able to connect from my apple laptop and other windows computers.  When I try to connect I get an error message stating the terminal session is not supported in my computer.  Can I connect to my office server using Maverik or do I have to revert to Mountain Lion?

    I talked with Apple support they tried having me restart my comp and reinstall intunes. Which did not work and he basically said that I would need to go the apple store and probably have to get a new phone. Thank god I backed everything up first.

  • Unable to start remote desktop connection broker

    somehow I could no longer start remote desktop connection broker service. I noticed that Windows image acquisition (WIA) service could be started manually and then it stopped by itself. I am not sure if they are related or not. From event viewer, I see some
    errors as follows (may be related):
    event 485 ESENT
    tssdis (2916) An attempt to delete the file "C:\windows\system32\edbtmp.log" filed with system error 5 (0x00000005):"Access is denied." The delete file operation will fail with error- 1032 (0xfffffbf8).
    Any clue or suggestion where I can look into?
    Thank you very much!!!!!

    Hi,
    Thank you for your posting in Windows Server Forum.
    register the below files using regsvr32
    regsvr32 %systemroot%\system32\wuapi.dll 
    regsvr32 %systemroot%\system32\wuaueng.dll 
    regsvr32 %systemroot%\system32\wuaueng1.dll 
    regsvr32 %systemroot%\system32\wucltui.dll 
    regsvr32 %systemroot%\system32\wups.dll 
    regsvr32 %systemroot%\system32\wups2.dll 
    regsvr32 %systemroot%\system32\wuweb.dll 
    regsvr32 %systemroot%\system32\softpub.dll
    In addition, also Try to disable UAC for your account and reboot, this might help to resolve your issue.
    Source:
    esent 485 event wuaueng.dll
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/27cd64d0-7ec7-4732-a2ac-4c36a0513690/esent-485-event-wuauengdll?forum=winservergen
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Remote desktop issues after OS upgrade

    I have a MACBook PRO that was loaded with MAC OS Snow Lepoard.  I use this laptop to connect back to work via Barracuda and it worked without any issues.  Now that I have updated to the Lion OS, can connect to the Barracuda site but when I attempt to connect to my computer the RDC crashes.

    2 questions.
    Have you downloaded the latest RDC version from Microsoft?
      Microsoft Remote Desktop Connection Mac OS X Client (free)
    <http://www.microsoft.com/mac/products/remote-desktop/default.mspx]]>
    Have you tried an alternative RDC client, such as CoRD
      CoRD (Microsoft RDC Screen Sharing)
    <http://www.macupdate.com/info.php/id/22770/cord>

  • I'm unable to set my desktop display after a Firfox update.

    Last evening Firefox performed an automatic update. After the update was completed, the photo on my desktop changed, and I am unable to change it by going to Control Panel> Desktop tab. I have a plain blue screen.

    Ah, OK! I've managed to recreate your problem. Here's the solution, it's a bit complex so read it through and ideally have it on screen on another computer or print it out first.
    1. Go to  > System Preferences > Users & Groups
    2. Hold down 'control' and click 'Login Options' near the bottom of the left-hand column
    3. Where it says 'Network Account Server' in the main window, click 'Join'.
    4. Ignore the input box in the pop-up dialogue, but click the button bottom-left that says ''Open Directory Utility...'
    5. Click the padlock at the bottom of the new box and enter your admin password.
    6. Go up to the 'Directory Utility' menubar at the top, and choose the menu Edit > Enable Root User
    7. Type in the same password that you use for your admin accont and press 'return'
    8. Go  > Log out (your user name)...
    9. In the login window, type 'root' for the user, and your admin password for the password.
    10. In the new desktop that appears, navigate to the file you want to lock. Do 'get info' and you'll NOW see that you can lock it!
    11. After locking the file, go  > log out (root user) and re-login in your usual account.
    Job done!

Maybe you are looking for