Skip to main content

Posts

Showing posts from November, 2018

How to Speed Up VMware Converter 6.2

1. Taking forever to P2V or V2V a server? Disable SSL on VMware converter. 2. Edit "converter-worker.xml" with your favorite editor. Your going to have to save it as another file name because if you attempt to edit the actual file. It will bark "Access Denied" errors. PATH: c:\programdata\vmware\VMware vCenter Converter Standalone 3. Open the "converter-worker" XML file and edit the section called: <useSsl>true</useSsl> and change it to <useSsl>false</useSsl> 4. Save the file as converter-worker-bak.xml. 5. Delete the original converter-worker.xml file and then remove the -bak from the one you created. 6. Re-launch VMware Converter and go after that migration!

Top 10 IT Certifications 2019

2019 is here already! Good grief! Time is flying. Ok. So here is your Top 10 IT Certifications for 2019. If you are not working in the cloud, seriously...stop playing around and get serious about your career before one of us hungry IT people eat your lunch! The days of playing guardian over an infrastructure and hiding what can be done in the cloud, in a colocation data center or offsite outside of your company, non-profit or organization are OVER. FUD (Fear, Uncertainty and Doubt) no longer will work to your benefit if your one of these dinosaurs in an organization scared of change. It will happen whether you like it or not. Drumroll!!! Hands-on IT Certifications where recruiters will blow up your LinkedIn with offers! 1. AWS Solutions Architect - Associate Level (Champion): https://aws.amazon.com/certification/certified-solutions-architect-associate/ 2. AWS Solutions Architect - Professional Level: https://aws.amazon.com/certification/certified-solutions-architect-profes

How to Configure a Default Login Screen for Windows 10 with Group Policy

1. Create a folder called "Logo" under NETLOGON 2. Add the image to the folder 3. Use  %logonserver% to identify multiple domain controllers since if you identify one specific DC and it goes down or there is any other problem with a particular DC, user's won't get the login screen image (the policy won't run on login). Example: \\%logonserver%\netlogon\Logo\w10-lock-screen.jpg 4. The GPO Setting is under Personalization under Computer Configuration

Migration from Exchange 2013 to Office365 Authentication Error

1. Verify that the Administrative user has the permission for "Application Impersonation" in the Exchange Admin Center. 2. Change all users in your local Active Directory over to the UPN for the verified (publicly resolvable Active Directory Domain). Powershell command: $LocalUsers = Get-ADUser -Filter {UserPrincipalName -like '*domain.local'} -Properties userPrincipalName -ResultSetSize $null $LocalUsers | foreach {$newUpn = $_.UserPrincipalName.Replace("domain.local","public.com"); $_ | Set-ADUser -UserPrincipalName $newUpn} 3. Sync your Azure Active Directory Tool (Force the Update) Start-ADSyncSyncCycle Start-ADSyncSyncCycle -PolicyType initial 4. Verify that your login with "public.com" is working on https://portal.office.com Username: stewie.griffin@public.com Password: test0! You call that a password? This is a password son!! : %&^*(LUIKG/73&^%HVJB)&*(YIU)(&*^UTY8567irtufgykA&*(^RTUFGYOHPI()

How to Fix Microsoft Exchange 2013 to Office 365 Error ews/mrsproxy.svc' failed.The HTTP request was forbidden with client authentication scheme ‎’Negotiate‎’

1. The first part of the denial is that the Exchange 2013 server has to be set to "0" instead of "1" in their attributes. 2. Login to your DC and then search for ADSI Edit (Windows 2012/2016/2019 Server): Change the "adminCount" setting to "1" and then reboot the server (NOTE: I saw that even on reboot, this flag remained. So I doubt it has anything to do with the http authentication.) This is when I then ran the following commands on the Exchange 2013 Server itself in EMS. This is the Microsoft article: https://support.microsoft.com/en-us/help/2975731/access-is-denied-error-when-you-try-to-move-mailboxes-to-exchange-onli but it had no impact at all on the error even after rebooting. It just came back. 3. Login to the CAS or Exchange Server and Open the Exchange Management Shell 4. Run the following command in the EMS: [PS] c:\Windows\system32\ Get-WebServicesVirtualDirectory | select *auth* 5. Look at the output for BasicAuthentic

Transfer FSMO Roles

1. Login with a forest level administrator account 2. Open CMD prompt as an Administrator 3. Run the following commands: ntdsutil - > roles -- > connections --> connect to server dc-servername -- > quit Schema Master transfer schema master <Enter Key> RID Master transfer rid master <Enter Key> Domain Naming Master transfer naming master <Enter Key> PDC Emulator transfer pdc <Enter Key> Infrastructure Master transfer infrastructure master <Enter Key> Type q / q and that's it! Shut the box down or do whatever you were going to do!