I’m sure anyone of you log onto server notice that server manger start automatically. This is particularly issue for remote desktop environment when regular user log in, they will be presented with server manger. I’ve no idea why Microsoft allow this in RDS environment in first place. Anyways, here how you can disable it for all users.
There is two way you can do this first via GP, which is my preferred method.
First bring up group policy editor and create a GP and navigate to Computer configuration, Administrative Templates, System, Server Manger and then open ” Do Not Display Server Manger Automatically at logon” and click enable.
Otherwise, ( But this will need to be run on each servers) run power shell in admin mode,
Get-ScheduledTask -TaskName Server Manger | Disable-ScheduledTask -verbose
This is very useful if you have system that you need to run commend without keep typing su in the beginning of the command line and then enter the sudo password.
Bring up terminal and ssh into the system ssh your host ip -l username and then enter the psw
You will be in the ssh line on the remote system.
Type sudo visudo and then the psw
add this line to the end of the file and save and done.
I love to experiment with various software and one of those essential system that I play around is kali. I’ve setup mine in ESXI server that I cannot directly connect. This is one of the way you can RDP into your kali and experience full GUI access.
Here is the codes that you need to run in sudo mode.
I know once in a while we all have to use our CMD skill to set some stuff up in machines. So here is some command to get windows machine online via CMD.
****First you need to locate the name of the network interface
netsh interface ipv4 show interfaces
***Assume that you want to setup a static IP such as below
IP:172.28.5.10
sub:255.255.255.0
GW: 172.28.5.1
netsh interface ip set address name=”Local Area Connection” static 172.28.5.10 255.255.255.0 172.28.5.11
Note that ” local area connection” is the one I found when I ran very first command and “1” in the end is the metric for route.
If you want to forget about the static rout and want to get DHCP,
netsh interface ip set address name=”Local Area Connection” dhcp
****Now if you want to set a static DNS,
netsh interface ip set dns name=”Local Area Connection” static 8.8.8.8
Second DNS
netsh interface ip add dns name=”Local Area Connection” 8.8.4.4 index=2
Again if you want to get DNS via DHCP
netsh interface ip set dnsservers name=”Local Area Connection” source=dhcp
DONE,your PC will be one line!!. Yes of course you need to plug the network cable 🙂
Computer communication via internet only can work if TCP/IP working properly. I’m sure you have seen after many ipconfig/renew/release and flushdns and REBOOT still PC cannot get IP. In my experience this is related to corruption in TCP/IP and of course you need to check the cable or WIFI is connected before all of this 🙂
Anyway here is how to reset those corrupted TCP/IP stack and make sure to reboot the PC after reset and RUN the command prompt in ADMIN mode.Also if you have static IP, remember to note them down, because this will wipe those out!
Before all of this in my experience resetting socket also can fix many ip stack related issues and here is the command.
If you are familiar with PENTEST and Kali linux platform, you should know nmap which is great vulnerability scanning tool. But recent version of kali has dropped ZENMAP which is GUI base for nmap which great tool to run nmap in GUI and also to generate command line to run on nmap.
Few of my blog readers mentioned to me that after Kali 2020.4 my previous method of installing Zenmap no longer works. So after breaking few VM images and few swear moment I was able to figure out a way to install Zenmap GUI in new Kali. 🙂
Then bring up terminal from the place downloaded the tar package and run sudo su and get the root access. After that run below command in sequence. Very good guide here https://nmap.org/book/inst-source.html
apt-get updatebzip2 -cd nmap-7.91.tar.bz2 | tar xvf -
cd nmap-7.91
./configure
make
su root
make install
then install each package with dpkg -i <each package name from above>
As a example dpkg -i ./python-cairo_1.16.2-2ubuntu2_amd64.deb
Once you down you will be able to see zenmap from search window in kali. But if you want to run Zenmap as root you need to brows into place where tar package got unzip. In my case download folder nmap 7.91 and bring terminal and run sudo su and then ./zenmap.
apt-get update apt-get install alien cd to the download folder where you download zenmap sudo alien “zenmap-7.80-1.noarch.rpm” sudo dpkg -i “zenmap-7.80-1.noarch.deb”
So if you are one of the user has mcafee antivirus, specially the drive encryption enabled, you will run into issue upgrading Win 10 patches or upgrade. Usually the error pretty similar to below,
So solution would be upgrading OS via mcafee switch enabled via CMD. Here is what I did,
*****Copy Windows update to C: folder called updates( This was 1903 update and I downloaded it as ISO from Microsoft site and then mount and copied to the folder)
******Then bring up CMD as administrator and type cd c:\update, which change the directory.
These days more and more PC/laptops comes with SSD drive and most of them are either 128 or 256 and some are even smaller drives. If you are one of the user don’t want top pay for more storage with iphone and backing up your phone to PC, you will face some challenge with drive space. Specially with ever expanding iphone storage size.
Issue is itunes saves this backups under userprofile, usually in C drive. Solution would be change this location and point to a external drive or different drive. All the credit should goes to https://support.imazing.com/hc/en-us
I’m gonna list the Windows way first.
Usual backup location for iphone located under C:\Users\*current user name*\AppData\Roaming\Apple Computer\MobileSync\Backup
Navigate to folder and rename or delete folder called “backup”
Then Shift+Right click and select open powershell windows OR you can bring command prompt (go to run type CMD) and the type
cd C:\Users\*current user name*\AppData\Roaming\Apple Computer\MobileSync
****Note that above I send my backups to D:\ drive.
and you done!!
So now in Mac OSx
Bacup folder located under ~/Library/Application Support
Go to search and type ~/Library/Application Support/MobileSync/ and this will point to backup location and as previous Windows remove the folder called backup.
Then bring up terminal and type
ln -s /Volumes/location where the backup should go/MobileSync/Backup ~/Library/Application\ Support/MobileSync/Backup
I know once in a while windows UAC tend to interfere with application. I seen many issues with some ERP programs. You can simply disable UAC via control panel in Windows 7 but Windows 10 will not completely disable UAC via control panel. Because if it completely disable metro app will not work on Win10.
This is reg edit to disable UAC completely, if you ever have to fight with it to get application working.
Few days ago I was doing office 365 migration and I had strange issue with outlook not picking up auto discover settings. End customer was setup with godaddy imap mail and want to move to office 365. I can see from 365 panel DNS was setup correctly but whatever the reason, mail client was keep going toward contoso.com instead autodiscover.contoso.com ( Yes I pick domain right out of the Microsoft teaching : )
Finally I ran Microsoft connectivity analyzer and it spit out below error,
We got an unexpected autodiscover response. We can see that your mailbox is in Office 365. However, AutoDiscover service seems to have configuration issues that prevent Outlook to connect o Office 365. An intermediate web server at https://contoso.com/Autodiscover/Autodiscover.xml is interfering with AutoDiscover service and responding with incomplete data.
To work around this issue if your administrator can’t resolve the above soon, please take the following action:
Create an Outlook registry key to exclude the HTTPS root domain. For more information about how to do this, see the following Microsoft Knowledge Base article: 2212902Important Excluding the HTTPS root domain is not a long-term solution for this issue. This workaround is provided as immediate relief for it. As soon as your administrator resolves the above AutoDiscover issue, the Outlook registry key must be removed. You need to either remove or correct the AutoDiscover component from https://contoso.com/Autodiscover/Autodiscover.xml. If https://contoso.com/Autodiscover/Autodiscover.xml is managed by a web hosting provider, please contact them, and make sure that the web server is not responding to Autodiscover requests.
I read through several auto discovery troubleshooting article but none point to correct solution but after few read through I found a article at go daddy portal https://ca.godaddy.com/community/Managing-Email/cPanel-and-Office-365-Autodiscover/td-p/27832 which point me to correct solution. Also last part of the above error log point to godaddy setup instead actually 365 or dns config error.
So this issue cause by godaddy cPanel pointing all mail request to particular domain to thier internal hosting server. I’m not sure why godaddy do this but again I’m not admin for godaddy.
Also this also cause headache if you are current office365 customer via godaddy setup but if you decide to go to office 365 and host your mail. Because I seen many posting related to issue with moving from godaddy version of 365 to MS direct office 365 exchange. But surprisingly godaddy tech support has no clue and also MS support. Ms support solution would be adding a reg key to stop going https look up for autodiscover but this won’t solve the problem with mobile devices.
Okey enough with rant and here is the solution,
Log into godaddy and from My Product page click mange next to domain hosting
Click on three dot and click on settings
Then click on cPanel admin
Then you will end up in cpanel and then go to email section and click on Email Routing
once you there configure email routing and select Remote Mail Exchanger and change.
Also you can click on Zone editor and edit correct MX entry and point that to office 365 mx entry.
After that mail client will point to correct place without and issue.
