red hat linux

1. connect to network. Modify the following network interface file

RedHat rhel no internet connection after install

vi /etc/sysconfig/network-scripts/ifcfg-ens33 (network interface)

https://www.youtube.com/watch?v=Skle0U2kvtE

2. https://access.redhat.com/solutions/253273

you need to register your new server. Create account on redhat and make sure go the developer portal for no-cost redhat registration

https://developers.redhat.com/articles/faqs-no-cost-red-hat-enterprise-linux#general

https://access.redhat.com/solutions/253273

subscription-manager register --username <username> --password <password> --auto-attach

3. install GUI, run (recommended)

# yum groupinstall "Server with GUI"

or For RHEL 7 Server you can target the "Server with GUI" group instead

# yum groupinstall "Server with GUI"

• After installing the appropriate packages, change the default systemd boot target to graphical.target. If you run into any errors, try updating the system first with 'yum update'.

systemctl set-default graphical.target

• To immediately switch to the GUI login, start the graphical.target:

systemctl isolate graphical.target

change the resolution in rhel applications -> system tool -> setting -> devices -> displays ->resolution

4 . mount to shared drive from windows 

https://www.youtube.com/watch?v=b14pq04jtDg

install samba protocol

sudo yum -y install samba-client samba-common cifs-utils

create a mapped folder

sudo mkdir -p /mnt/sharedfolder

sudo mount.cifs -v //WINBOX01/shared /mnt/winbox01 --verbose -o user=brainstrust,password=topsecret,domain=WINBOX01

check the mapped folder

df -kh

5. sudo yum install java-1.8.0-openjdk-devel

6. sudo yum install firefox

7. sudo -i -- to change to root

8. su -l user or exit to the user you have logged in with

9. /etc/ssh/sshd_config to open ssh port 22 (or others)

10. su root (switch to root)

Username is not in the sudoers file

11. edit /etc/sudoers

Let’s add a line under the user privilege specification. Its purpose is to grant the system user the mentioned superuser privileges:

# User privilege specification
root	ALL=(ALL:ALL) ALL
francis  ALL=(ALL:ALL) ALL

Now francis can perform tasks that require root access.

Shortly after making the change, we need to save these changes and exit from the text editor. To do this, we’ll press the keyboard keys CTRL+X to exit, Y to save, and Enter to submit. Finally, we can exit from the root session.

12. Adding the Username to the sudo GroupAs in the solution above, it’s important that we first switch to the root user:

$ su root
Password: 

The su command allows us to perform tasks with the permissions of another user, which in this case is root.

13. Next, we’ll show the contents of the sudoers file. We’ll focus on the lines that declare the privileges of users, as well as those of user groups:

# cat /etc/sudoers
...

# User privilege specification
root	ALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo	ALL=(ALL:ALL) ALL

...

As shown above, the root user and the members of the admin and sudo groups have superuser privileges. Then again, the sudo group is present, since we’re in a Debian-based distribution. In a Red Hat-based Linux distribution, we’ll encounter the wheel user group instead. It’s the equivalent of the sudo user group for Red Hat-based distributions.

Now, since we’re operating in Debian, let’s add our user to the sudo group:

# usermod -aG sudo francis

Here, the usermod command allows us to modify our user’s attributes. In particular, we use the -G option to declare that we’d like to update the group information for our user francis. Also, the -a option makes certain that other groups associated with this user aren’t deleted in the process. As a result, francis can now perform administrative tasks with sudo. In Red Hat distros, replacing sudo with wheel provides similar results.

Once we’re through, we’ll exit from the root user session:

# exit
exit

Now we’re back to our previous user session.

rm -r -f * (silently delete subfolders and files)

 

Import-Module ActiveDirectory

$SampleDate = Get-Date -Format g

 

 

$status= Get-ADUser -Filter * -SearchBase 'ou=CA,dc=dshs,dc=wa,dc=lcl ' -Properties displayname, givenname, initials, sn, description, title, physicaldeliveryofficename, telephonenumber, mail, streetaddress, l, st, postalcode, manager, department, location, samaccountname, employeeID, distinguishedName,created|

select displayname, givenname, initials, sn,  description, title, physicaldeliveryofficename, telephonenumber, mail, streetaddress, l, st, postalcode, manager, department, location, samaccountname, employeeID, DistinguishedName, created

C:\Scripts\SQLInsertObject1.ps1 $status -server "databaseserver" -db "CATSAMDB" -sql "select * from ADUSER_CA_Users" -truncateTable $True

fix ax timeout issue

 

This is what needs to happen on the DB:

 

For AX FamLink error collision of object id which causes AX to refuse any further imports – a data fix in the ae_seq table resolved the issue. – which causes an appid to show as negative in the DB.

 

DB – needs to be modified – so someone with the ability to modify the DB needs to make the change.

 

To fix a negative appid

update ae_seq set appid = 8 where appid = -8

 

 

Other queries to run:

Query – run and it should not retrieve any results

 

SELECT docid, COUNT(*) TotalCount

FROM ae_dt186

GROUP BY docid

HAVING COUNT(*) > 1

ORDER BY COUNT(*) DESC

 

Query to show if there are any duplicate doc IDs:

 

SELECT docid, COUNT(*) TotalCount

FROM ae_dt8

GROUP BY docid

HAVING COUNT(*) > 1

ORDER BY COUNT(*) DESC

 

To find last doc id

select MAX(docid) from ae_dt8

 

AX Applications and Corresponding App ID:

 

 

create cert for azure VPN

makecert.exe has been deprecated.

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\makecert.exe" -sky exchange -r -n "CN=PlazRootCert" -pe -a sha1 -len 2048 -ss my "PlazRootCert.cer"

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\makecert.exe" -n "CN=PlazVPNClientCert" -pe -sky exchange -m 96 -ss my -in "PlazRootCert" -is my -a sha1

powershell for self signed certificate

$cert = New-SelfSignedCertificate -Type Custom -KeySpec Signature -Subject "CN=PlazRootCertVM" -KeyExportPolicy Exportable -HashAlgorithm sha256 -KeyLength 2048 -CertStoreLocation "Cert:\CurrentUser\My" -KeyUsageProperty Sign -KeyUsage CertSign

New-SelfSignedCertificate -Type Custom -DnsName P2SChildCert -KeySpec Signature -Subject "CN=PlazVPNClientCertVM" -KeyExportPolicy Exportable -HashAlgorithm sha256 -KeyLength 2048 -CertStoreLocation "Cert:\CurrentUser\My" -Signer $cert -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.2")

azure VPN gateway has many sku but basic is out of the list in azure portal but you can create it with powershell script.

$vnet = Get-AzVirtualNetwork -Name VNET1 -ResourceGroupName dcyf

$subnet = Get-AzVirtualNetworkSubnetConfig -name 'GatewaySubnet' -VirtualNetwork $vnet

$ngwpip = @{

    Name = 'PLAZVPN_Gateway_Public_IP'

    ResourceGroupName = 'dcyf'

    Location = 'westus2'

    Sku = 'Basic'

    AllocationMethod = 'Dynamic'

    IpAddressVersion = 'IPv4'

}

New-AzPublicIpAddress @ngwpip

$ngwpip = Get-AzPublicIpAddress -Name PLAZVPN_Gateway_Public_IP -ResourceGroupName dcyf

$gwipconfig = New-AzVirtualNetworkGatewayIpConfig -Name PLAZVPN_Gateway_Public_IP_Config -SubnetId $subnet.Id -PublicIpAddressId $ngwpip.Id

New-AzVirtualNetworkGateway -Name PLAZVPN_Gateway_VNET1 -ResourceGroupName dcyf -Location "westus2" -IpConfigurations $gwipconfig -GatewayType "Vpn" -VpnType "RouteBased" -GatewaySku "Basic"

1. create root cert

2. create client cert issued by root cert.

3. create vpn gateway through portal or command

4. add configuration to add root cert (public key only) 

5. download vpn client and install on local machine

6. install client cert (pfx) to the cert mmc.

---------------------------------------------------------------------------------------

https://www.youtube.com/watch?v=Yshpo6V1qUQ

https://www.youtube.com/watch?v=aa5b0t9bZy0

https://learn.microsoft.com/en-us/azure/vpn-gateway/

download cert with openssl and IEChooser.exe

openssl.exe s_client -connect <domain.company.com>:<port>

C:\Windows\System32\F12\IEChooser.exe

check .net framework and .net core version

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match '^(?!S)\p{L}'} | Select PSChildName, version\

dotnet --list-runtimes

Configure WildFly in Domain mode

 

reference: http://www.mastertheboss.com/jbossas/jboss-as-7/jboss-as-7-domain-configuration/

How to configure WildFly in Domain mode

29 October 2012 by F.Marchioni

A WildFly Domain consists in grouping several WildFly instances into one single group (or a “server-group” using the WildFly nomenclature). In fact, we group the WildFly server into one logical server-group, and all the WildFly instances will share the same configuration. By this we intend that they share the same WildFly profile ( default , ha , full , and full-ha ), same deployments, and so on. In this tutorial we will show all the steps to configure a WildFly Domain.

In order to configure our domain we will at first configure the Domain Controller and its domain.xml configuration file. Next we will configure the hosts where the applications will be deployed.

Domain controller set up (domain.xml)

The server configuration of the domain is centralized in the domain.xml file of the domain controller. The domain.xml is located in the directory $JBOSS_HOME/domain/configuration. It includes the main configuration for all server instances. This file is only required for the Domain Controller.
In the domain.xml file we will define the server group configuration (which can be anyway changed at runtime, as we will see in a minute).

<server-groups>

<server-group name="main-server-group" profile="full">

<jvm name="default">

<heap size="64m" max-size="512m"/>

</jvm>

<socket-binding-group ref="full-sockets"/>

</server-group>

<server-group name="other-server-group" profile="full-ha">

<jvm name="default">

<heap size="64m" max-size="512m"/>

</jvm>

<socket-binding-group ref="full-sockets"/>

</server-group>

</server-groups>

This domain configuration reflects the following schema:

As you can see, we have two server groups: main-server-group and other-server-group. You can in turn associate each server group with a different profile.
The default configuration includes four preconfigured profiles:

• default – Support of Java EE Web-Profile plus some extensions like RESTFul Web Services or support for EJB3 remote invocations
• full – Support of Java EE Full-Profile and all server capabilities without clustering
• ha – default profile with clustering capabilities
• full-ha – full profile with clustering capabilities

A profile contains the configuration of the supported subsystems that is added by an extension. We choose the full profile which contains all WildFly / JBoss EAP capabilities, except for clustering.
The referenced profile will be assigned by the server group to one socket-binding group. A socket-binding group references to logical interface names instead direct to the interfaces of a host. These logical interfaces are defined in the <interfaces> section of the domain.xml configuration file.

<interfaces>

<interface name="management"/>

<interface name="public"/>

<interface name="unsecure"/>

</interfaces>

The exact binding of the interfaces with the IP address is done into the host.xml file, however we will leave it with the default values and use start up properties to override these values.

Configuring the host.xml of the Domain controller

The first thing we need to check, is that the host controller acts as domain controller. This is stated by the domain-controller element:

<domain-controller>

<local/>

</domain-controller>

Next, since we won’t add any server on this host, we need to state it, using an empty servers element:

<servers />

Last thing we need to do, is creating a management user which will be used to authenticate from the other host controllers, when connecting to the domain controller. For this purpose we will use the add-user.sh shell script which is located in the bin folder of JBOSS_HOME folder:

$./add-user.sh
 
What type of user do you wish to add? 
 a) Management User (mgmt-users.properties) 
 b) Application User (application-users.properties)
(a): a

Enter the details of the new user to add.
Realm (ManagementRealm) : 
Username : admin1234
Password : 
Re-enter Password : 
Are you sure you want to add user 'domain' yes/no? y

About to add user admin1234 for realm 'ManagementRealm'
Is this correct yes/no? y
Added user 'admin1234' to file '/standalone/configuration/mgmt-users.properties'
Added user 'admin1234' to file '/domain/configuration/mgmt-users.properties'

Is this new user going to be used for one AS process to connect to another AS process e.g.
slave domain controller?
yes/no? y

To represent the user add the following to the server-identities definition  
<secret value="ZnJhbmsxMjMh" />

TIP! You can use the add-user.sh in non interactive mode to create the management user and show the secret. Ex: add-user.sh -u admin1234 -p Password1!

Now we can start the domain controller with the following command. We will set the physical network bind address to the host configuration with the jboss.bind.address.management property. The management interface must be reachable for all hosts in the domain in order to establish a connection with the domain controller.

domain.sh -b 192.168.1.1 -Djboss.bind.address.management=192.168.1.1

(Please note the -b parameter is an alias for the -Djboss.bind.address parameter)

Slave configurations

After configuring the Master node, we will configure the Slave servers, where applications will be deployed. For this purpose we will set up two Slave Hosts. On each host we need also an installation of JBoss EAP / WildFly
On each host we need to configure the host.xml file (as an alternative you can name the host file as you like and start the domain with the the –host-config parameter. Example ./domain.sh –host-config=host-slave.xml ).
The first thing is to choose a unique name for each host in our domain to avoid name conflicts. So, configure the name “server1” on the first host.xml file:

<host name="server1" xmlns="urn:jboss:domain:1.4">

...

</host>

And for the other host:

<host name="server2" xmlns="urn:jboss:domain:1.4">

...

</host>

Next, we need to specify that the host controllers will connect to the remote domain controller. We will not specify the actual IP address of the Domain controller but leave it as a property named jboss.domain.master.port.
Additionally, we need to specify the username which will be used to connect to the Domain controller. So let’s add the user admin1234 which we have created on the Domain controller machine.

<domain-controller>

<remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}"

username="admin1234" security-realm="ManagementRealm"/>

</domain-controller>

Finally, we need to specify the Base64 password for the server identity we have included in the remote element:

<management>

<security-realms>

<security-realm name="ManagementRealm">

<server-identities>

<secret value="ZnJhbmsxMjMh" />

</server-identities>

<authentication>

<properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>

</authentication>

</security-realm>

<security-realm name="ApplicationRealm">

<authentication>

<properties path="application-users.properties" relative-to="jboss.domain.config.dir" />

</authentication>

</security-realm>

</security-realms>

<management-interfaces>

<native-interface security-realm="ManagementRealm">

<socket interface="management" port="${jboss.management.native.port:9999}"/>

</native-interface>

</management-interfaces>

</management>

The last step is to add the server nodes inside the host.xml file on both hosts.

So we will configure on the first host (server1):

<servers>

<server name="server-one" group="main-server-group"/>

<server name="server-two" group="main-server-group" auto-start="false">

<socket-bindings port-offset="150"/>

</server>

</servers>

And on the second host (server2)

<servers>

<server name="server-three" group="other-server-group"/>

<server name="server-four" group="other-server-group" auto-start="false">

<socket-bindings port-offset="150"/>

</server>

</servers>

Please notice the auto-start flag indicates that the server instances will not be started automatically if the host controller is started.
For the second server a port-offset of 150 is configured to avoid port conflicts. With the port offset we can reuse the socket-binding group of the domain configuration for multiple server instances on one host.

Ok, now we are done with our configuration and we can start the first host with:

domain.sh \
  -b 192.168.0.2  
   -Djboss.domain.master.address=192.168.0.1 
   -Djboss.bind.address.management=192.168.0.2

and the second one with:

domain.sh \
  -b 192.168.0.3  
   -Djboss.domain.master.address=192.168.0.1 
   -Djboss.bind.address.management=192.168.0.3

If you look at the Domain controller console, you should notice the following output which shows that the Domain controller has started and the other slave hosts have successfully connected:


[Host Controller] 14:43:40,740 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two

[Host Controller] 14:43:40,763 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registered remote slave host server-one

14:43:41,053 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'

[Host Controller] 14:43:43,757 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 00466fa4 (inbound) of Remoting connection 2f2990bf to localhost/127.0.0.1:46062 of endpoint "master:MANAGEMENT" ]

[Host Controller] 14:43:43,867 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registered remote slave host server-two

[Host Controller] 14:43:43,881 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 20.0.0.Final (WildFly Core 12.0.1.Final) (Host Controller) started in 8551ms - Started 80 of 82 services (25 services are lazy, passive or on-demand)