The Geek Squad

When you Fitbit Versa 2 struck with 'Unlock with your Phone' Unlock via Fitbit App : -Go to the Fitbit App, click 'Today' > Your profile picture > Choose your Versa 2 device -Select 'Device Lock', unlock the device with your pin code Factory / Hard reset Fitbit Versa 2 : Note : All your Versa 2 data will be deleted by this and you have start setting it up from scratch.  -Hold the left button for about 10 seconds, until you see the Fitbit logo -Keep holding the button, until the Fitbit logo disappears  -Release the button for about 2 seconds and start holding the left button again -After 5 to 8 seconds, you will feel a vibration -Then you may try to re-configure your Versa 2 as a new device -There are chances where you get an error 'Data not cleared Sync & try again' -Go to the below URL for the solution, Fitbit Versa 2 - Data not cleared Sync & try again

We renewed the Certificate in our Exchange 2016 Edge server and subscribed them to the Exchange 2016 Mailbox Server, then we started noticing the below mentioned event ID's in Edge and Mailbox role servers.  Event ID: 1005 in Exchange 2016 Edge Server Could not decrypt EdgeSync credential cn=ESRA.EDGESERVERNAME.HUBSERVERNAME.1,CN=Services,CN=Configuration,CN={XXXXX} using Edge default certificate with thumbprint XXXXXXX, The exception is The parameter is incorrect. Please unsubscribe and resubscribe your Edge Transport server Event ID: 2018 in Exchange 2016 Mailbox Server Outbound direct trust authentication failed for certificate CN=New_Cert_Name,O=Org_Name,L=City,C=Country. The target IP address of the Exchange Server that Microsoft Exchange tried to authenticate to is [IP]. Make sure EdgeSync is running properly. What we validated? -Ensured the SMTP Service assigned to the certificate is Valid and not Expired -Validated and Restarted the Active Directory Web Services, Microsoft ...

The Mail.que database file in Exchange Servers increases drastically after a point of time is an expected behavior, below are the possible reasons for them. Data stored in Mail.que file : Email message live traffic Shadow queue Emails pending for delivery & Submission queue Use the below path to reach the mail.que database file, Note: It is highly advisable to exclude this path from AntiVirus scanning. %ExchangeInstallPath%\TransportRoles\data\Queue Mail.que utilizing high space : Emails in queue due to sudden flooding during peak business hours or unavailability of other Exchange server Increased message expiration time, nethold time. The cmdlets to re-configure these values are in below article Note: The mail.que database file will not shrink, however during the online maintenance WhiteSpace will be accumulated which could be used for future emails  How to re-create Mail.que database file? Re-creating the mail.que database file will not harm your Exchange server...

The need of the scripting never ends, the usage of the date and time in them are always need with perfection. Below are the few PowerShell cmdlets to get the Year, Month, Dates and Time which you could utilize in your reports, scripts and automated emails.  Year : Get-Date -UFormat %Y (Year in expanded format e.g., 2020) Get-Date -UFormat %y (Year in shortened format e.g., 20) Month : Get-Date -UFormat %B (Month in expanded format e.g., October) Get-Date -UFormat %b (Month in shortened format e.g., Oct) Get-Date -UFormat %m (Month in number e.g., 10 for Oct) Day : Get-Date -UFormat %A (Day in expanded format e.g., Sunday) Get-Date -UFormat %a (Day in shortened format e.g., Sun) Time : Get-Date -UFormat %R (Time in 24 Hour format) Get-Date -UFormat %r (Time in 12 Hour format) Add or Minus Days and Time : ((Get-Date).AddDays(2)).addHours(-1)  - (Add days and Min Hours) ((Get-Date).AddDays(0)).addHours(1)   - (Add Hours) Short String & Long String for Date an...

When you attempt to run any Install-Module or Find-Module cmdlets and get the below error, Error : WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2/' Solution : Run the PowerShell as Administrator and run the below cmdlet, which will enable the TLS 1.2 in the PowerShell which should allow you to execute the Install-Module cmdlets, [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Note : You may run the below cmdlet to check current protocol type used by your PowerShell and also after running the above mentioned cmdlet and ensure it is updated.  [Net.ServicePointManager]::SecurityProtocol

 You may run the below cmdlet to check the PowerShell version, $PSversionTable Note: This cmdlet is applicable for below operating systems, Windows 7, Windows 8, Windows 8.1 & Windows 10 Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 & Windows Server 2019 Tip 💡 In order to get an unclipped output in PowerShell, please run the below cmdlet first and then run the actual cmdlet to get an unclipped output. $FormatEnumerationLimit=-1