I have installed Microsoft Remote Desktop 8.0.5 For MAC OSX 10.8.5 and added new remote connection in the list which works fine.
Now i export same connection to .rdp file but when i execute it mstsc opens remote os login screen and asks for user password to login (which is already in keychain store).
how can i launch .rdp file so that it will not ask remote user password?
where/how to store password?
------- .RDP File ----------
screen mode id:i:0
use multimon:i:1
session bpp:i:32
full address:s:192.168.1.130
audiomode:i:0
username:s:mylabs\administrator
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:0
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop composition:i:1
bookmarktype:i:3
use redirection server name:i:0
Thanks in advance
This article helped me
https://serverfault.com/questions/962628/failure-connecting-to-a-cyberark-managed-server-using-macos
Use Microsoft RDP Client for Mac starting from version 10.2.2
Run the following command on the Mac Terminal
defaults write com.microsoft.rdc.macos ClientSettings.EnforceCredSSPSupport 0
Close terminal and try to connect
Related
i am facing an issue while using the mac. I need to use that PowerShell command on my mac to run application as domain user
runas /netonly /user:user_name "C:\Users\fwa\AppData\Local\Programs\Azure Data Studio\azuredatastudio.exe"
I have tried
sudo -u user_name /Applications/AzureDataStudio.app
it asks password for local user. but in my case user is on External domain
To run Azure Data Studio (ADS) on your mac and login to SQL Server using Windows authentication instead of a username/password, you use the kinit command. I've had best luck using the kinit command through the built-in command window in ADS (you'll be prompted to do so if/when your login fails). Note that your computer needs network access to a kerberos server.
There's some further information about setting this up HERE and HERE.
I'm facing strange issue with WinSCP: It works well and I'm able to connect to remote hosts. But when I try to use the "Open session in PuTTY", instead of logging me directly with same credentials, PuTTY gets "stuck", prompting me to "login as".
I've checked the config in WinSCP and it looks fine: "Remember session password and pass it to PuTTY" is ticked.
What else should I check?
I'm using WinSCP 4.2.7 and PuTTY 0.60.3.
As documented:
By default, WinSCP creates temporary site settings for PuTTY (under the name "WinSCP temporary session"). The site settings will contain only the options known by WinSCP, mostly connection options. It will particularly lack any terminal options, so the defaults (Default Settings profile) will apply.
If you want to configure your own options, you can save PuTTY site settings with the same name as a WinSCP site. WinSCP will then instruct PuTTY to open that session (It will not export any settings, nor a connection options).
So if you have an invalid stored session in PuTTY with the same name as your WinSCP stored site, the "Open in PuTTY" function won't work, as it tries to open that invalid site.
Side note: You are using an obsolete and insecure versions of WinSCP and PuTTY. You urgently need to upgrade!
WinSCP is somehow looking into PuTTY saved sessions that are configured. I had a saved session in PuTTY with same name as in WinSCP ("myApplication - integration"). Somehow, when the session already exist in PuTTY, WinSCP is not able to log me in directly to PuTTY.
I deleted the saved session from PuTTY, and it worked: now WinSCP logs me in directly in PuTTY. And now I see a "WinSCP temporary session" in the list of saved session in PuTTY.
We need provide putty path
Right click the putty icon in WinSCP then go to Queue -> Customize -> Application
then provide your putty.exe path using browse button
then click ok
Now click the putty icon button from WinSCP, Putty will open automatically :)
In WinSCP Go to :
preferencce - > integration -> application
under "putty/terminal client path" add this line :
%ProgramFiles%\PuTTY\putty.exe -t -m "%TEMP%\putty.txt" !cmd.exe /c echo cd '!/' ; /bin/bash -login > "%TEMP%\putty.txt"
I tried to reset administrator password from following steps is below but unable to change administrator password.
Set the server computer to boot from USB Bootable drive, and boot the server from Windows server bootable image.
2.When install options appear, I select repair windows by command.
3.When command prompt appears, I type in command prompt "net user administrator password123" to reset the new password to the administrator user.
4.And reboot the computer after reboot I tried to login with new password but unable to login.
So please help me.
You can use offline nt password and registry editor. Here http://pogostick.net/~pnh/ntpasswd/ is the original source.
I am trying to make a script to install more or less automatically oracle database as well as some other application of my own. I haven't writen a line yet because I want to make all steps manually first.
So, my environment is the following. I have RHEL 5 with no graphic interface. I am connecting to the server from Windows laptop through SSH as root. I have enabled XForwarding, so when I login with root account I can run xdpyinfo so that I can check XServer configuration.
I need XForwarding because the Oracle DB installation procedure requires an XServer. However, Oracle requires the user oracle to perform the installation. I have already created the oracle user but when changing the user from root to oracle I can no longer run xdpyinfo command so the Oracle installation procedure fails. I get the following error:
Xlib: connection to "localhost:10.0" refused by server
Xlib: PuTTY X11 proxy: wrong authorisation protocol attempted
xdpyinfo: unable to open display "localhost:10.0".
I have tried to use xhost to enable my laptop to access my server but I have failed as well to do that.
If you really feel the need to do this, then while you are root, get the current $DISPLAY value, particularly the first value after the colon, which is 10 in your case. Then find the current X authorisation token for your session:
xauth list | grep ":10 "
Which will give you something like:
hostname/unix:10 MIT-MAGIC-COOKIE-1 2b3e51af01827d448acd733bcbcaebd6
After you su to the oracle account, $DISPLAY is probably still set but if not then set it to match your underlying session. Then add the xauth token to your current session:
xauth add hostname/unix:10 MIT-MAGIC-COOKIE-1 2b3e51af01827d448acd733bcbcaebd6
When you've finished you can clean up with:
xauth remove hostname/unix:10
That's assuming PuTTY is configured to use MIT-Magic-Cookie-1 as the remote X11 authentication protocol, in the Connection->SSH->X11 section. If that is set to MDM-Authorization-1 then the value you get and set with xauth will have XDM-AUTHORIZATION-1 instead.
It might be simpler to disconnect from root and start a new ssh session as oracle to continue the installation, which would also make sure you don't accidentally do anything unexpected as root. Well, until you have to run root.sh, anyway.
If you do a silent install with a response file then you don't need a working X11 connection anyway; you just need $DISPLAY to be set, but nothing is ever actually opened on that display so it doesn't matter if xdpyinfo or any other X11 command would fail. I'm not sure how you're thinking of scripting the X11 session, but even if that is possible a silent install will be simpler and more repeatable.
I got Postgres 8.4 installed on my mac with Snow Leopard. I know the 'postgres' user was created but I have no idea what the default password is. How should I login to the database?
http://archives.postgresql.org/pgsql-admin/2001-10/msg00192.php and similar internet resources may answer your question. Supposedly, there is no password by default.
For future readers...
I had a similar problem. After installing Postgres 9.1, the password I supplied to the installer didn't allow me to connect to the database using pgadmin 3. This is what I had to do to fix it:
Configure so you can log in without a password:
Stop the postgres server (launch daemon):
sudo launchctl unload /Library/LaunchDaemons/com.edb.launchd.postgresql-9.1.plist
Edit data/pg_hba.conf and change 'md5' to 'trust' in the 'local'
'127.0.0.1/32' line.
Start the daemon
sudo launchctl load /Library/LaunchDaemons/com.edb.launchd.postgresql-9.1.plist
Connect using pgadmin 3 and re-set the password
Start pgadmin 3 and connect to the database (right click 'Connect' on the Postgres 9.1 server).
Under Login roles, right-click the 'posgres' user, select 'Properties...' and reset the password on the 'Definition' tab panel.
Then disconnect pgadmin 3 from the database (right-click 'Disconnect' on the Postgres 9.1 server).
Configure the server so it requires a password again:
Stop the daemon (as per step 1.1).
Edit data/pg_hba.conf and change 'trust' back to 'md5' in the
'local' '127.0.0.1/32' line.
Start the daemon (as per step 1.3).