HOWTO: Win2k8R2 Reset Local Administrator Password

How to Change a Local Administrator Password with Group Policy

We will use Group Policy Preferences to set password on local user account

• Click Start – All programs – Administrative Tools – Group Policy Management.
• Create or Edit Group Policy Objects.
• Expand Computer Configuration – Preferences – Control Panel Settings.
• Right-click Local Users and Groups – New – Local User.
• Ensure the Action is Update and enter the new password.
• If this is a one-time change (not permanent):
  • Go to the Common tab and check the box for “Apply once and do not reapply“.
• If the change should be permanent: The defaults are correct.

Here is an image of what the policy should look like before applying it:

How to Change a Local Administrator Password with Group Policy

Note: By default, all Group Policy updates are applied on a 90-minute timer. To apply the update instantly, run a gpupdate /force on the machine to be affected.

 

 

In the Original Post Can Read:

– Update all Computers Local Users Passwords at once

See the Original Post from Microsoft: http://social.technet.microsoft.com/wiki/contents/articles/4683.how-to-change-a-local-administrator-password-with-group-policy.aspx

 

Advertisements

FIX: freeradius-as-dhcp ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user: .. SOLUTION!!

The exact error from radiusd -X

ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user

QUICKTIP: Official Signatures for mail servers AV, ANTISPAM testings

Just put the code signature in your email body or where you want

Anti virus test: EICAR-STANDARD-ANTIVIRUS-TEST-FILE

X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

Anti Spam test: 
XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X

FIX: creating template1 database in /usr/local/pgsql/data/base/1 … FATAL: could not create shared memory segment: Function not implemented

When starting initdb on postgresql into FreeBSD jail , with normal (default) config the error message appears and exits the init proccess:

The error message: creating template1 database in /usr/local/pgsql/data/base/1 … FATAL:  could not create shared memory segment: Function not implemented

This is because of sysvipc kernel security.

To Fix this, in the host machines edit two files:

1. Append to /etc/rc.conf:
   jail_sysvipc_allow=”YES”
2. Append to /etc/sysctl.conf:
   security.jail.sysvipc_allowed=1

FIX: FreeBSD Jails Create exit with error Messages in logs and stdout: kernel: usage: expr [-e] expression Mar 31 12:03:03 smtp-xs root: /etc/rc: WARNING: jail_extract_address: type not identified

UNKNOWN SOLUTION OR REASON. NO TIME TO DEBUG YET.

OffTopic:

Please , there is no mount_devfs in FreeBSD. Please do not use quick internet tutors for everything!!!

use mount -t devfs and that’s all about this error message.

 

HOWTO: Create FreeBSD 10.2 for serving jails and jails configurations – SHELL SCRIPT

Here is the simple script for creating new jails:

 

#!/bin/sh
HOSTNAME=’###########’
JAILDIR=/usr/jails/$HOSTNAME
mkdir -p $JAILDIR/dev
mkdir -p $JAILDIR/etc
mkdir -p $JAILDIR/usr/tmp
chmod 777 $JAILDIR/usr/tmp
cd /usr/src/usr/src/
make buildworld                                                                     # COMMENT OR REPLACE BUILDWORLD IF IT’S ALREADY BUILD
make installworld DESTDIR=$JAILDIR
cd /usr/src/usr/src/etc
cp /etc/resolv.conf $JAILDIR
make distribution DESTDIR=$JAILDIR NO_OPENSSH=YES NO_OPENSSL=YES  # If you dont need ssh to the jail
cd $JAILDIR
mount -t devfs devfs $JAILDIR/dev                                     # At this point we’ll mount devfs, and then hide the unneeded devs
devfs -m $JAILDIR/dev rule -s 4 applyset
ln -s dev/null kernel                                                                    # Create a null kernel
touch $JAILDIR/etc/fstab                                                        # Quell warnings about fstab
cp /etc/resolv.conf $JAILDIR/etc/resolv.conf                     # Use our existing resolv.conf
mkdir -p $JAILDIR/etc/ssl                                                       # Copy our settings for ssl
mkdir -p $JAILDIR/usr/local/openssl
cp /etc/ssl/openssl.cnf $JAILDIR/etc/ssl
cd $JAILDIR/usr/local/openssl/
ln -s ../../../etc/ssl/openssl.cnf openssl.cnf
echo Make a decent rc.conf:
echo hostname='”$HOSTNAME”‘ # Set this!
echo ifconfig_em0=”inet 10.0.0.20 netmask 255.255.255.255″
echo defaultrouter=”10.0.0.1″ # Set to default gateway (or NO).
echo clear_tmp_enable=”YES” # Clear /tmp at startup.
echo kern_securelevel_enable=”YES”                                   # kernel security level (see init(8))
echo kern_securelevel=”3″                                                       # Once you set your jail up you may want to consider adding a good securelevel: Same as sysctl -w kern.securelevel=3

HOWTO: PostgreSQL 9.4 Streaming Replication Automatic Failover with repmgr PART 2: using repmgr WITNESS

Continue from: https://iamsto.wordpress.com/2016/01/21/howto-postgresql-replication-with-automatic-fail-over-using-repmgr-a-k-a-replication-manager/

 

In this case we have 3 servers in the setup: DB_MASTERNODE, DB_SLAVENODE, DB_WITNESS , where our db_witness server is the server which host the application.

 

Initialize the witness server PostgreSQL Data dir structure and promote the server as witness in the database cluster:

# su - postgres
-bash-4.1$ /usr/pgsql-9.4/bin/repmgr -d repmgr -U repmgr -h rw-db1 -D /var/lib/pgsql/9.4/data -f /etc/repmgr/9.4/repmgr.conf --initdb-no-pwprompt witness create ; tail /var/log/repmgr/repmgr-9.4.log

-bash-4.1$ repmgr -f /etc/repmgr/9.4/repmgr.conf cluster show

[2016-01-23 11:01:20] [NOTICE] Redirecting logging output to ‘/var/log/repmgr/repmgr-9.4.log’
Role | Connection String
* master | host=MASTERNODE dbname=repmgr user=repmgr
standby | host=SLAVENODE dbname=repmgr user=repmgr
witness | host=MASTERNODE dbname=repmgr user=repmgr