I have to monitor many servers (over 3000) and the management has decided to use MobaXterm. All right, it works fine.
The ideal would be to have sessions already set up and shared with colleagues, it would be a considerable convenience.
Is there a way to massively import server data (name, ip, login) into sessions instead of insert them one by one?
From the Sessions tab, left click User sessions and select Import sessions from file
The file should be similar to the following image.
The version is Personal Edition v11.0.
MobaXterm is able to import sessions from a list of hosts, but this is limited to the import of hosts without users/port/passwords/advanced settings.
For that, you have to create a file with one server per line.
Then, in order to try this feature, you can start a local terminal and run the "ServersListToMxtSessions.sh" script.
The script will ask you to select a file, so just select the one you have created.
Hope it helps....
MobaXterm is able to import sessions either from:
The file in .mxtsessions format.
You can export few examples first to see the syntax, so you can write a script to save it into that format.
PuTTy/SuperPuTTy sessions.
All sessions from PuTTy can be imported. To import into PuTTy, you can create a registry file.
Other session formats (check the contextual menu in Sessions for full list).
Alternatively use a macro app to achieve that (such as AutoHotkey).
To import mRemoteNG connections into MobaXterm, you need to export the mRemoteNG connections file in name "confCons.xml" specifically (Otherwise MobaXterm won't recognize it as potential file for import)
Once you have your mRemoteNG connections file named as "confCons.xml", go to:
MobaXterm -> Import sessions from third-party programs -> Import from MRemote sessions -> Choose the exported "confCons.xml"
Related
I want to install apex app. I know of two ways to install any app.
Importing export file via Apex designer interface from the same workspace
Or, copy the app export file let's say f101.sql and execute that as script directly in SQL developer using the database Schema (which is connected to workspace)
I want to do something similar like 2, but instead of using same Schema, I want to use different Schema to execute script but install into the same workspace.
Example: f101.sql is app export of workspace finance_ws, which is connected to finance_schema of database.
I have another schema deployment_schema. Could I execute f101.sql file in deployment_schema so that it gets deployed in finance_ws workspace?
I'd
create a new workspace (let's call it deployment_ws)
designate it to deployment_schema
create a developer in that workspace (let's call it arif)
connect to deployment_ws as arif
import f101.sql
Perhaps you can do it as you wanted, but ... I find the above approach simpler.
[EDIT]
You'd want to have only one workspace (which is FINANCE_WS), but import F101.SQL into it so that one application works on finance_schema, and another one on deployment_schema.
As you can't have two applications with the same ID, you'll have to import F101.SQL and change application ID during import (that's on the "Install application" tab. Use either "auto assign new application ID" or "change application ID" (manually).
On the same import page, you'll see the Parsing schema property - change it to deployment_schema. If you don't see it in the list of values, connect as admin into internal workspace and designate deployment_schema to finance_ws.
I guess that's what you, actually, wanted ...
deployment_schema should have APEX_ADMINISTRATOR_ROLE assigned. Once assigned, we can deploy/execute any app through deployment_schema in any workspace which exist in that database
We have a standard config (tunnel.conf) for Wireguard that we want to push to clients (via JAMF Pro).
We do not want the end user to have to open the Wireguard UI to import the config, we want to do this via scripting.
Given I can place the tunnel.conf file anywhere on the end user's system, where do I have to place it, and what command do I need to run to import it?
And conversely, how can I delete a tunnel config from Wireguard, via scripting?
So, as it turns out, Wireguard has a unique key-pair per tunnel - which means each user has their own keys.
Managing that via JAMF sounds like a nightmare, and it'll be easier to point users at their accounts in the VPN to pull down their config, than to manage it for them. Documentation and handholding time!
But it seems to be possible to manage applying a profile via automation. The kind support people at my VPN provider pointed me to this article on JAMF community board:
https://community.jamf.com/t5/jamf-pro/wireguard-configuration-file-distribution/m-p/264747
There's a related page on the wireguard-apple repository:
https://github.com/WireGuard/wireguard-apple/blob/master/MOBILECONFIG.md
If we do end up trying to manage the users configs, I'll update here.
How can I export to file my Server Group configurations in Azure Data Studio?
I've created a Workspace file in my application solution that contains useful queries for troubleshooting, etc. I'd like to also include connection configurations for servers relevant to the solution so that any developer can use the Workspace queries quickly without having to ask which servers to run them on.
You can copy your Server Group configurations from User Settings. You will find them under datasource.connectionGroups and connection details under datasource.connections (if you have different ones, check with the group id). Any user can copy paste them into his user settings except the password. Everyone needs to add it after that. I would suggest to create a JSON file with those settings and add the steps to readme.md file.
All connections and groups are located in the settings.json file located at:
%AppData%\azuredatastudio\User\
For me specifically the path looked like this:
C:\Users\MyLogin123\AppData\Roaming\azuredatastudio\User
We have number of jobs configured in Controlm and now we got new environment to configure same set of jobs,
Is there any way to create controlm jobs from backend server by writing shell or any scripts?
Any other possibilities to avoid spending time in creating same jobs again and again for each environment??
Control-M provides the functionality to export/import jobs across environments : https://communities.bmc.com/docs/DOC-50416
There are a couple of ways:
From the Planning domain, load the job folders you want to migrate into a blank workspace.
from the top bar then click Export and save. This will save a .xml file you can edit using a text editor and then Import Workspace and load - you can import the .xml into the same Control-M if environments are on one CTM EM Server, or a different CTM EM Server.
OR
From the planning Domain, load the job folders you want to migrate, right click on the folder and select Duplicate, then through the GUI update the new folder (If doing this I'd then unload the source folder just to ensure nothing is overwritten there). You can use the Find & Update option. This will only work if your environments are on the same CTM EM server.
I'm working on a tool that generates .rdp files and then invokes them using Microsoft RDP Client. This tool is running on Mac OS.
Everything works well, the only problem is that I can't figure out of how I can generate 'password 51:b' field properly. On Windows this can be done easily by using CryptProtectData method from Crypt32.dll library. How can I do the same on Mac.
Another option could be to use "rdp://" URL scheme, but it doesn't seem allow to pass password this way.
So the question is how can I implement auto-login on Mac if I use third-party RDP client.
As far as i know you can't. You can however create a "User Account" and a Server configuration and add both to the client. The connection will then be visible on the main window and you just need to double click it.
To do so, you need to add the password to the Keychain, use /usr/bin/security to do so from a script. It needs to be a generic-password and saved in com.microsoft.rdc.macos. Also be sure to generate an ID according to the RDP Clients scheme, like BFF77777-7777-7777-7777-777777777777.
You may also set the permissions to read that key using /usr/bin/security and set-generic-password-partition-list specifying the right teamid (UBF8T346G9) and again com.microsoft.rdc.macos. You need the admin password to do this step.
Then you can alter the RDP Clients config file, which is a .sqlite file located at /Users/$(whoami)/Library/Containers/com.microsoft.rdc.macos/Data/Library/Application Support/com.microsoft.rdc.macos/com.microsoft.rdc.application-data.sqlite. Add the user configuration in the ZCREDENTIALENTITY table and make sure the ZID matches the one added to the keychain.
To add a server configuration you need to alter the ZBOOKMARKENTITY table. Just add a configuration by hand using the UI and look at the table to get a feeling of how it needs to be setup. Basically you link your user configuration with the server configuratio by making sure that ZCREDENTIAL in ZBOOKMARKENTITY matches Z_PK in ZCREDENTIALENTITY of your user configuration.
I know the answer is a bit late, but it may give you a starting point. This will however not fully automate the process, you will still need to go to the UI and double click the connection you want to use.