Friday, June 9, 2023

Windows Updates Got The 0x80248007 Blues

Does your winders updates have the 0x80248007 blues?

1. Hold down the Winders Key and Press R. Type services.msc and enter.  If you are running as a standard user (you not be running with admin privileges), I like to run a command prompt by right click run as administrator.  Then you can type services.msc into the command prompt to run services.msc with elevated privileges. 

2. In the Services window, find the Windows Update and right-click it to select Stop.

3. Using the File Explorer or command prompt, navigate to the partition or drive where Windows is installed. Find the following path.  Usually this will be the C:\SoftwareDistrobution\DataStore

4. Delete everything in the DataStore folder.

5. Now go to C:\SoftwareDistrobution\Download and delete everything. 

6. You can now go back to services.msc and start the Windows Update service.

7. Find Windows Update or Automatic Updates, right-click it and select Start from the context menu.

Now you should be able to check for updates again to be sure everything is working.

Tuesday, May 2, 2023

Powershazzille Exchange Folder Size


From the Lazy Admin.  Cool dude Connect to Exchange Online with PowerShell - The Best Method (lazyadmin.nl)

1.  Launch an elevated PowerShell window

2.  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
        a. Say Y

3.  Install-Module -Name PowerShellGet -Force
        a. Say Y

4.  Install-Module -Name ExchangeOnlineManagement -Force

5.  Update-Module -Name ExchangeOnlineManagement

6.  Connect-ExchangeOnline -UserPrincipalName john@contoso.com

Now that you are connected you can run the next command to get the folder size information.  Replace username with the user you want to look up.

7.  Get-MailboxFolderStatistics username | Select Name,FolderSize,ItemsInFolder

When you finish, don't forget to disconnect

8.  Disconnect-ExchangeOnline



Friday, March 10, 2023

Installing .mis and .exe packages with Intune


1.       Go to this link and download the converter.  If you want more instructions, click here.

2.       After downloading the IntuneWinAppUtil.exe, you may want to move it over to an easy to find folder on your computer.

3.       Run IntuneWinAppUtil.exe and follow the prompts.  The file will ask you for the following.

a.       Folder location of your source .msi or .exe

b.       The filename of the .msi or .exe

c.       The destination of the new .intunewin file we are creating

4.       Now you can head on over to endpoint.microsoft.com>Apps>Windows

a.       Click Add

b.       Select the app type Windows app (Win32)

c.       Select the .intunewin file you created earlier

d.       Fill out all the important information.  I like to be sure and add a logo image to make it easier for end users if you are going to allow them to select it in the company portal.

e.       Install command: if you converted a MSI the field should already be populated.  If you converted an exe file, you would use the setup.exe /s command in the

f.        The quest for the uninstaller

                                                               i.      You will need to run this powershell script to find the uninstaller identifying number.

                                                             ii.      get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize

                                                           iii.      Now you will need to put the msiexec.exe /x {unique identifying number from step 1} /qb command in the uninstall command in your Intune Win32 Application

Tuesday, January 10, 2023

M365: Whitelisting Stuff Against My Better Judgment

 Well, there are a few options on M365 when looking for where mail flow is hanging up.  I've never been really sure why you have to add it in multiple places.  Probably has something to do with the service it hits first in the mail flow.

  • Sometimes it helps to add a mail flow rule "admin.exchange.micros>Mail flow>Rules"
    •  Add a new rule but just remember to enable it.  
  • Another option is to take a look at the SPAM filter "Security.microsoft.com>Email & collaboration>Policies & rules>Anti-Spam policies>Anti-spam inbound policy (Default)"
  • Policies & rules > Threat Policies >Preset security policies.  Select the policy you want and then walk through the wizard until you get to the Impersonation protection section.  Then you will eventually come across the trusted senders and domains feature.

.Net said .No so this says .Youbetterorelsebuddy

 I was having trouble with .net framework install on new computers.  I'm not sure why it didn't work repeatedly, but found that if y...