First from virtual machine menu, click Devices and click on Insert Guest Addition CD Image. This process will add guest addition CD inside VM.
Bring terminal and run below,
sudo apt updatesudo apt install build-essential dkms linux-headers-$(uname -r)
Then brows into the CD from GUI interface and right click somewhere in the CD and click open terminal here. This bring Terminal within CD
then simply run,
sudo su
./VBoxLinuxAdditions.run --nox11
You will need to reboot VM.
“The Volatility Framework is a completely open collection of tools, implemented in Python under the GNU General Public License, for the extraction of digital artifacts from volatile memory (RAM) samples. ” Volatility GitHub
Kali Linux has dropped volatility from their new release and you won’t be able to install it as usual apt-get install. You can go to GitHub and get info to install it via volatility download https://www.volatilityfoundation.org/releases. But when you start running it you will see many error pop up. This mainly due to no python availability in new debian and missing dependencies.
It took me few hours of fiddling around with various package install and reading through many post. But this is the method I was able to test and get it working.
Big thanks to Jason @ Jase IT and whoever did post to install python2 @ https://stackoverflow.com/questions/61981156/unable-to-locate-package-python-pip-ubuntu-20-04
Sudo su
apt-get update
###Install phython2
apt install python2
####Install pip2
curl https://bootstrap.pypa.io/get-pip.py –output get-pip.py
python2 get-pip.py
If Error happened run below and then run python2 get-pip.py
curl https://bootstrap.pypa.io/2.7/get-pip.py –output get-pip.py
###Install python3
apt install python3
###Install pip3
apt install python3-pip
###Install dependency
apt-get install pcregrep libpcre++-dev python-dev -y
###Upgrade setuptool
pip2 install –upgrade setuptools (make sure it is dash dash before upgrade setuptools NOT single dash)
###Install pip dependency
pip2 install pycrypto
pip2 install distorm3
###Download and extract volatility from https://www.volatilityfoundation.org/releases listed as “Source Code”
###CD into the location source code
python setup.py install
python vol.py -h to see more info
I’ve recently face an error with Kali Linux install in VMware Player and even after giving ample enough space /resources it was keep falling with install step failed and I’ve confirm that VM installer has internet access.
This is pretty much loop back even after restart the install. I’ve tried many times and different methods to install and come back to screen saying hit continue and it will bring up menu that you can skip the step of installing software, pretty much you will loose the GUI and all Kali packages.
After few hours browsing and cursing this the method I used to get kali install and functioning.
**** Basically hit continue and once you come to next step where you have option to skip,skip the step and installer will continue but when kali boot back you will be presented with basic debain shell.
****Log into the shell with your username and password then run these in a order and reboot. Make sure that your Kali can reach to the internet.
This command will install GUI XFACE, after install you will be able to log into Kali GUI.
***sudo apt-get install kali-desktop-xfce
Then you need to update kali install,
***sudo apt update
After this kali need to download base tool set via meta package install. This step will install base Kali tool and some other top tools. You can refer to this link for Kali meta packages in detail https://tools.kali.org/kali-metapackages
*** sudo apt update && sudo apt install kali-linux
*** sudo apt update && sudo apt install kali-linux-full
Here is a great blog post to install meta packages https://githacktools.blogspot.com/2018/04/how-to-install-kali-linux-metapackages.html
You may have seen error 0x800f081f while trying to repair windows with DISM command. It is usually looks like below,
This is the command sequence to fix it,
*** dism /online /cleanup-image /checkhealth
***Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
***If Above came as yes run Dism.exe /online /Cleanup-Image /StartComponentCleanup
***DISM /Online /Cleanup-Image /RestoreHealth
My case above didn’t work for whatever the reason and had to mount original server install ISO and ran below command and repair via WIM file in OS install ISO
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\Sources\Install.wim:1/limitaccess ( X was the drive letter for my ISO)
Make sure to run all command in Admin mode in CMD.
This method apply to upgrade Dell ESXI server 6.7 U1 to U3
Go to Dell vmware esxi u3 patch download page https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=j75ny
Download VMware-VMvisor-Installer-6.7.0.update03-14320388.x86_64-DellEMC_Customized-A02.zip file and upload in to your ESXI datastore.
Put the host to maintenance mode.
Then ssh into esxi host via putty and run this command
esxcli software vib install -d /vmfs/volumes/Store1/updates/VMware-VMvisor-Installer-6.7.0.update03-14320388.x86_64-DellEMC_Customized-A02.zip
make sure to to change store location and zip file name as per your environment.
After the completion, reboot the esxi
Done!!
As Cisco jabber released a new version to fix some security vulnerabilities, I had a opportunity to mass update the existing jabber versions. Below is tested script that I used to successfully deploy the Jabber 12.9.1 version to all Windows endpoints. You can edit this as needed and deploy Jabber 12.9.1. My script basically removed existing Jabber 12.8.1 and 12.6.2 and install latest 12.9.1.
REM Uninstall Jabber 12.8.1
“msiexec.exe” /x {6E87407E-2EFD-4C7F-B167-8219279226E6} /qn /norestart
REM Uninstall Jabber 12.6.2
“msiexec.exe” /x {BEFF5578-DB83-4AFA-8C40-4A005F2A3BF9} /qn /norestart
REM Delete regkey Jabber 12.6.2
reg delete “HKEY_CLASSES_ROOT\Installer\Products\8855248850B85EC4787609E82C36C6B2” /f
REM Delete regkey Jabber 12.8.1
reg delete “HKEY_CLASSES_ROOT\Installer\Products\7D843DE4BA2A2DC4C89F532E22C06EC9” /f
REM Install Jabber 12.9.1
msiexec.exe /i \share location\CiscoJabberSetup.msi /qn CLEAR=1
This post mainly refer to Cisco Catalyst switches and this I have tested on production network without any issues. But again proceed with caution!!. Cisco recommend to have a CA trust point configured on all the Cisco devices for secure communication. But if you do not have one switch will fall back to a self-sign certificate which we need to renew over the time. This is the full article from Cisco https://www.cisco.com/c/en/us/support/docs/security-vpn/public-key-infrastructure-pki/215118-ios-self-signed-certificate-expiration-o.html
Also great community article https://community.cisco.com/t5/networking-documents/a-self-signed-certificate-is-added-to-a-cisco-catalyst-switch/ta-p/3124222
Here are the steps for how to do it in short form,
*** SSH into the switch or console connect.
***show crypto pki certificates —– to get the certificates and show you all the certificates. This will show you all the switch certs and you will be able to locate expired one.
***Locate the ID of the cert that has expired date and it will usually show you something like TP-self-signed-51XXXXXX
***Switch to privilege mode
***no ip http secure-server ——-disable https server before do any renewal
*** no crypto pki trustpoint TP-self-signed-51XXXXX —- this id you were located running first command
***ip http secure-server ———re enables the https server and generates a new trustpoint and certificate
*** do show crypto pki certificates – check the new cert is there with new validity period
Then you are done.
Few Weeks back I had the chance to upgrade SQL server from 2012 to 2016 which host SCCM DB. Usually SQL Upgrades are very straight forward process. You can read a very good article about how to do SQL upgrade here. https://www.virtualizationhowto.com/2017/03/how-to-upgrade-sql-server-2014-to-sql-server-2016/
But after straight forward upgrade and testing everything was fine except SCCM, reporting will not load and was throwing an error Failed to load expressions host assembly. But SQL server was working without an any error.
After looking through many logs I was able to located the issue which was cause by SQL file location changes during the upgrade. Then I had to brows through the internet to find a solution and Microsoft recommend solution was to reinstall Reporting Service Point (RSP) role which is describe here https://social.technet.microsoft.com/wiki/contents/articles/15475.how-to-successfully-install-reporting-services-point-role-in-sccm-2012-sp1.aspx
But I wasn’t dare enough to go and mess around SCCM and found very good solution here https://ronnydejong.com/2013/05/23/reporting-service-point-rsp-broken-after-upgrading-sql-server-2012-sp1-sysctr/ This was listed solution for upgrade from 2008 to 2012 but same solution worked for my situation also.
****Basically, copy srsresources.dll from old SSRS install location which was in my case was in \Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Report Server\Bin
TO
New SSRS location \Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\Report Server\Bin
****Then find rssrvpolicy.config file in new SSRS install (\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\Report Server\Bin) open with note pad
****Then search for the SRSResources URL within note pad and change the URL to new location where DLL copied in first step.
Then you are done.
Recently, I had to renew one of the remote desktop server farm SSL certificate. There are many instructions and videos for renewal of self-sign SSL for RDS gateway but there are only few places I was able to find anything for trusted SSL renewal.
In this blog I’ve used images from windowsserveressentials.com ( https://windowsserveressentials.com/2012/06/20/renew-your-ssl-certificate-sbs-2011-essentials/), because I really didn’t have chance to take snapshot of every step I did and cannot risk leaking any info on servers I worked on( if I forget to black out some parts 🙂 ). But basically cert renewal is the same and no difference initially with few important changes. Server I worked was 2016 Server.
****First, open IIS Manger and click on Server name.
****Then click on server certificate about to expire and right hand top corner click on create certificate request and this will bring up certificate request wizard. In this fields make sure to fill the name as exactly as current rds gateway name and choose bit length as 2048.
****Then save the cert request where ever you want. But I usually save to the root C:\Cert\2020. So I can keep track on old certs too. Just in case if I need old one I’ve it close by. This a text file with all the crypto info.
Then head to your favourite SSL provider and complete the cert renewal. My cert provider was Go daddy and usually godaddy auto renew SSL but cannot use this SSL due to the fact that it is missing private key info from the server. So basically click on cert and copy and past entire certreq.txt file info and request the SSL from Go daddy.
****Then Go daddy will do it things and send out email to whoever mange domain to confirm cert renew. In this case I had access to the email account who mange the domain. Once you go daddy issue cert go ahead and choose IIS as a cert and download to the server cer location. I choose C:\certs\2020.
****Then we gonna go to next step and open IIS Manger again and same place click on complete cert renewal. Then select the CA issues cer and name the cert complete the request which will install new SSL on IIS.
****After cert install SSL need to bind into port 443 in order to be active.
****So we are done with SSL for IIS, then need to assign cert for RD Gateway. Open TS Gateway Manager and right-click the local TS Gateway server, and then click Properties.
****On the SSL Certificate tab, click Select an import and it will show certificate just install in IIS and you can simply install it. After that Click OK to close the Properties dialog box for the TS Gateway server.
*****After this step you are done and RDS gateway will show with proper cert.
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
Done!!
NetSideTech 