
Brandon Bunnelle
"IT Administrator" for Express Packaging, Inc. based out of NE Ohio.
Activity overview
Latest activity by Brandon Bunnelle-
Brandon Bunnelle commented, I have SMBv1 completely disabled on all of my Windows 7 desktops as well as the Windows 10 desktops and have no issue hitting the Admin Share on any of my machines. I also administrate all of my ma...
-
Brandon Bunnelle commented, If you're looking to exclude 2016 from the reporting just change the reports Registry Key to the full value of 2010 to find those machines with only 2010. See below: Obviously, replace the "Office...
-
Brandon Bunnelle commented, There are no idiots here. Asking questions is the smartest thing anyone can do! We all learn together. PS: Yes it's cheesy but its true.
-
Brandon Bunnelle commented, Jonathan, It's not a digression as those registry values "must" be present to have a successful install of Office. Something has gone terribly wrong during your uninstall/install process. You are t...
-
Brandon Bunnelle commented, One more thing... If it's a 32-bit version of Office installed on a 64-bit OS, your registry path is "HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\"
-
Brandon Bunnelle commented, Jonathan, The registry path that Stephen gave you is the correct registry path for all Office applications installed on your machine. Inside of "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curren...
-
Brandon Bunnelle commented, Microsoft is notorious for doing this kind of thing. I always encourage those who have the capacity to spin up a WSUS server, to do so to help mitigate these issues. With that said, I know that doe...
-
Brandon Bunnelle commented, From what I am reading online it seems that error "2359303" against "KB3178690" carries some registry flaws with it. I am doing a little more digging on the issue.
-
Brandon Bunnelle commented, Create a Command step and use the following: %SYSTEMROOT%\System32\Wusa.exe /uninstall /kb:3178690 /quiet /norestart
-
Brandon Bunnelle commented, Did you try to run this as "Local Machine" in your deploy step?