Windows Activation

How To Fix "An Unauthorized Change Was Made To Windows  Server 2008" Error

In my case, the problem was with the Windows Activation. The activation of my windows had ended (3 Year Activation). But it was very important for me to continue with this copy of Windows Server 2008, as it was not feasible for me to switch this Live Server serving Dozens of clients.

So, in order to get myself into the Windows Server 2008, I used the below mentioned steps to fix the issue with my Windows Activation.

1) Click the option that launches an Internet Browser (on the error screen which reads Learn More Online)

2) Type: %windir%\system32 into the address field (To access the Windows System32 directory)

3) Find the file cmd.exe

4) Right-click on cmd.exe and select Run as Administrator

5) Type the following command on the Command Prompt: 

cscript %windir%\System32\slmgr.vbs /ilc %windir%\System32\licensing\ppdlic\Security-Licensing-SLC-ppdlic.xrm-ms)

6) Hit the Enter key

7) Reboot twice.

Conclusion

You need to reboot your machine Twice in order to fix this Issue. After following the above steps, I was able to fix the issue with my Windows Activation. But, if the issue is not solved by following the above steps, then you need to check if your Antivirus is causing this issue. If so, please uninstall the Antivirus software from your machine. Hope this solves the Issue.

RMAN commands

rman target sys/opera10g
show all;
crosscheck backup;
delete noprompt expired backup;
crosscheck archivelog all;
delete noprompt expired archivelog all;

PPTP Bruit Force

/ip firewall filter
add action=drop chain=input comment="pptp brute force drop 1/4 - complete comunication DROP" disabled=no \
src-address-list=pptp_blacklist_DROP
add action=add-dst-to-address-list address-list=pptp_blacklist_DROP address-list-timeout=10m chain=output comment="pptp brute force drop 2/4" \
content="bad username or password" disabled=no dst-address-list=pptp_blacklist_stage_2 protocol=gre
add action=add-dst-to-address-list address-list=pptp_blacklist_stage_2 address-list-timeout=1m chain=output comment="pptp brute force drop 3/4" \
content="bad username or password" disabled=no dst-address-list=pptp_blacklist_stage_1 protocol=gre
add action=add-dst-to-address-list address-list=pptp_blacklist_stage_1 address-list-timeout=1m chain=output comment="pptp brute force drop 4/4" \
content="bad username or password" disabled=no protocol=gre

Unifi AP factory reset via SSH

syswrapper.sh restore-default

Linux

After changing ip address config

$ sudo ip addr flush interface-name
$ sudo systemctl restart networking

Unifi install in Ubuntu 16.04

https://community.ubnt.com/t5/UniFi-Wireless/UniFi-Installation-Scripts-UniFi-Easy-Update-Scripts-Works-on/td-p/2375150

NEC SV9300

Name assign - CM77-Y1
EXT create - CM1X -YY00
Digital- F+ext no.
CO - D + trunk no.
Analoge - ext no.

Checking before delete-
CM12- Station data
01and 04

Trunk Data
CM30
CM77 trunk route name
CM35 assign trunk name -03

Initial trunk access assign
CM20
Code - A081

Oracle Transaction code and AR re-link

select trx_code,description,AR_NAME_ID from trx$_codes where resort='STRAND' and trx_code='9041'


Update trx$_codes set AR_NAME_ID='2739737' where resort='STRAND' and trx_code='9041'

Error 1920 (SepMasterService) failed to start" and Endpoint Protection fails to open

This problem may occur if one or more of the following conditions are true:

• Log file or database corruption exists in the %Systemroot%\System32\Catroot2 folder.
• Cryptographic Services is set to disabled.
• Other Windows files are corrupted or missing.
• The timestamp signature or certificate could not be verified or is malformed.
• The hidden attribute is set for the %Windir% folder or one of its subfolders.
• The Unsigned non-driver installation behavior Group Policy setting (Windows 2000 only) is set to Do not allow installation or Warn but allow installation, or the Policy binary value is not set to 0 in the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Non-Driver Signing
• The Enable trusted publisher lockdown Group Policy setting is turned on, and you do not have the appropriate certificate in your Trusted Publishers certificate store.
  This Group Policy setting is located under User Configuration, under Windows Settings, under Internet Explorer Maintenance, under Security, under Authenticode Settings in the Group Policy MMC snap-in.
• You are installing Internet Explorer 6 SP1, and the 823559 (MS03-023) security update is installed.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  828031  "The software you are installing has not passed Windows Logo testing..." error message when you try to install Internet Explorer 6 Service Pack 1
• The software distribution folder is corrupted.
• There is an "Image File Execution Options" Debugger value in the registry for the ccSvcHst.exe process. Such a value may have been put in place by malware to attempt to block the installation. Navigate in the registry to this key:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
  Delete the "ccSvcHst.exe" key if it exist. For a 64-bit machine repeat the check under:
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options

Delete Failed DCs from Active Directory

Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.
To clean up metadata

1. At the command line, type Ntdsutil and press ENTER.

PowerShell

1 2	C:\WINDOWS>ntdsutil ntdsutil:

2. At the Ntdsutil: prompt, type metadata cleanup and press Enter.

PowerShell

1 2	ntdsutil: metadata cleanup metadata cleanup:

3. At the metadata cleanup: prompt, type connections and press Enter.

PowerShell

1 2	metadata cleanup: connections server connections:

4. At the server connections: prompt, type connect to server <servername>, where <servername> is the domain controller (any functional domain controller in the same domain) from which you plan to clean up the metadata of the failed domain controller. Press Enter.

PowerShell

1 2 3 4

server connections: connect to server server100 Binding to server100 ... Connected to server100 using credentials of locally logged on user. server connections:

Note: Windows Server 2003 Service Pack 1 eliminates the need for the above step.

5. Type quit and press Enter to return you to the metadata cleanup: prompt.

PowerShell

1 2	server connections: q metadata cleanup:

6. Type select operation target and press Enter.

PowerShell

1 2	metadata cleanup: Select operation target select operation target:

7. Type list domains and press Enter. This lists all domains in the forest with a number associated with each.

PowerShell

1 2 3 4

select operation target: list domains Found 1 domain(s) 0 - DC=dpetri,DC=net select operation target:

8. Type select domain <number>, where <number> is the number corresponding to the domain in which the failed server was located. Press Enter.

PowerShell

1 2 3 4 5 6

select operation target: Select domain 0 No current site Domain - DC=dpetri,DC=net No current server No current Naming Context select operation target:

9. Type list sites and press Enter.

PowerShell

1 2 3 4

select operation target: List sites Found 1 site(s) 0 - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net select operation target:

10. Type select site <number>, where <number> refers to the number of the site in which the domain controller was a member. Press Enter.

PowerShell

1 2 3 4 5 6

select operation target: Select site 0 Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net Domain - DC=dpetri,DC=net No current server No current Naming Context select operation target:

11. Type list servers in site and press Enter. This will list all servers in that site with a corresponding number.

PowerShell

1 2 3 4 5

select operation target: List servers in site Found 2 server(s) 0 - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net 1 - CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net select operation target:

12. Type select server <number> and press Enter, where <number> refers to the domain controller to be removed.

PowerShell

1 2 3 4 5 6 7 8 9

select operation target: Select server 0 Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net Domain - DC=dpetri,DC=net Server - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net DSA object - CN=NTDS Settings,CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net DNS host name - server200.dpetri.net Computer object - CN=SERVER200,OU=Domain Controllers,DC=dpetri,DC=net No current Naming Context select operation target:

13. Type quit and press Enter. The Metadata cleanup menu is displayed.

PowerShell

1 2	select operation target: q metadata cleanup:

14. Type remove selected server and press Enter.

You will receive a warning message. Read it, and if you agree, press Yes.

Sponsored

PowerShell

1 2 3

metadata cleanup: Remove selected server "CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net" removed from server "server100" metadata cleanup:

At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed from the domain controller.

15. Type quit, and press Enter until you return to the command prompt.

To remove the failed server object from the sites

16. In Active Directory Sites and Services, expand the appropriate site.
17. Delete the server object associated with the failed domain controller.

To remove the failed server object from the domain controllers container

18. In Active Directory Users and Computers, expand the domain controllers container.
19. Delete the computer object associated with the failed domain controller.

20. Windows Server 2003 AD might display a new type of question window, asking you if you want to delete the server object without performing a DCPROMO operation (which, of course, you cannot perform, otherwise you wouldn’t be reading this article, would you…) Select “This DC is permanently offline…” and click on the Delete button.

21. AD will display another confirmation window. If you’re sure that you want to delete the failed object, click Yes.

To remove the failed server object from DNS

22. In the DNS snap-in, expand the zone that is related to the domain from where the server has been removed.
23. Remove the CNAME record in the _msdcs.root domain of forest zone in DNS. You should also delete the HOSTNAME and other DNS records.

24. If you have reverse lookup zones, also remove the server from these zones.

Other considerations
Also, consider the following:

• If the removed domain controller was a global catalog server, evaluate whether application servers that pointed to the offline global catalog server must be pointed to a live global catalog server.
• If the removed DC was a global catalog server, evaluate whether an additional global catalog must be promoted to the address site, the domain, or the forest global catalog load.
• If the removed DC was a Flexible Single Master Operation (FSMO) role holder, relocate those roles to a live DC.
• If the removed DC was a DNS server, update the DNS client configuration on all member workstations, member servers, and other DCs that might have used this DNS server for name resolution. If it is required, modify the DHCP scope to reflect the removal of the DNS server.
• If the removed DC was a DNS server, update the Forwarder settings and the Delegation settings on any other DNS servers that might have pointed to the removed DC for name r

ESXI NIC driver install

01. Upload the VIB to a datastore which is visible by your ESXi 5.5 host (“drobo01″ in my case)
02. Make sure that you enable SSH and connect via Putty
03. Set the acceptance of the host to “community supported”

esxcli software acceptance set –level=CommunitySupported

04. use this command to install the VIB

esxcli software vib install -v /vmfs/volumes/drobo01/VMware_bootbank_net-r8169_6.011.00-2vmw.510.0.0.799733.vib

05. Reboot your host

Configuration-Setup-Screen Design-Screen Painter

Configuration-Setup-Screen Design-Screen Painter

Send emails from PHP with ssmtp

The installation process:

sudo apt-get install ssmtp

Then edit the /etc/ssmtp/ssmtp.conf file with this information:

mailhub=smtp.gmail.com:587
UseSTARTTLS=YES
AuthUser=<YOUR-EMAIL>@gmail.com
AuthPass=<YOUR-PASSWORD>

(or any other SMTP-server that you might want to use)

Final steps:
Find your php.ini file (usually in /etc/php5/cli/php.ini) and make sure the sendmail_path is:

sendmail_path = /usr/sbin/sendmail -t

Then restart your apache2-server with

service apache2 restart


In my case, I've got a hosted server so I needed to edit this file :

/etc/ssmtp/ssmtp.conf

Then uncomment this line :

FromLineOverride=YES

Windows License Reset

cscript %windir%\System32\slmgr.vbs /ilc %windir%\System32\licensing\ppdlic\Security-Licensing-SLC-ppdlic.xrm-ms