@dashrender said in pricing on websites:

Why and to what end?

I don't have my hourly rate on there. The reason for that is I have a different hourly rate for different clients.

@darek-hamann said in BSOD on virtual server 2016:

Have you tried removing any faulty drivers from safe mode?

I don't know what the faulty drivers are. I removed the printer drivers I don't need through print management and haven't had a blue screen yet, but only time will tell.

Well done Jared.

I'll start off by saying I don't because every client and every project is different.

I have seen a couple people bash vendors that don't publish pricing on their websites. How many of you have pricing on your website?

Does this help:
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/2a0dc55d-66c4-4228-a834-0389a32e52b0/how-can-i-use-powershell-to-copy-an-excel-worksheet-from-one-workbook-to-the-second-sheet-of-another?forum=ITCG

Easy decision for me. I have no need to learn Cisco stuff because I don't have any clients with a Cisco router. What is your client base/environment?

@scottalanmiller said in I can't even:

LOL, that thread is super weird. And the OP doesn't appear to have responded... quite fishy.

I get the first time posters that ask how to get their laptop to boot and stuff like that. A post about starting a MSP as a first post?

@scottalanmiller I want to start a MSP thread-

I saw that too and since it was his first post figured that someone is trolling us.

From Webroot:

To be compatible with the release of the Windows 10 Fall Creator update build 1709, we have made available our SecureAnywhere endpoint version 9.0.18.44. If you are considering updating to the Windows 10 Fall Creator update build 1709, we strongly recommend updating your SecureAnywhere endpoint version to our 9.0.18.44 release. This will ensure that when you update your system, your security will be compatible with the upgrade.

To install this latest version of Webroot, you can either update your current version of Webroot endpoint or you can uninstall and reinstall using our latest endpoint download available via the Webroot Admin Console > "Resources" tab.

To force an update to the latest version, please use the "Agent Commands" option from within the Webroot admin console. From the "Sites" tab of the console, click to manage the specific site in question > Endpoint Protection > Group Management > Agent Commands > Advanced > Download and Execute a File.

http://anywhere.webrootcloudav.com/zerol/wsasme.exe

You can also use the URL above to download the installer locally on the endpoint via a browser, and run manually.

@dbeato said in BSOD on virtual server 2016:

By the way what Xerox drivers do you get? Are using the PCL6

I am using the PCL 6. Not sure if it was the global driver. In the process of that driver not rolling, I also installed the PS, PCL5, and XPS. I have since removed the extra drivers and the old drivers from the Konica that the copier replaced.

@scottalanmiller said in BSOD on virtual server 2016:

For a second I was terrified that the capitalization was wrong and that MS made a new version of Virtual Server 2005!

oh, I wanted to be clear it's a VM since most BSODs are caused by drivers and VMs don't have all the third party drivers that physical boxes do.

What would be calling the script? As Scott says, just call the .ps1 and forget about using a .bat

The clients had an issue with one of the two Xerox drivers because of an issue with Webroot and the Windows 10 creators update. An update from Webroot fixed the problem.

@dustinb3403 said in BSOD on virtual server 2016:

Doesn't BlueScreenView work with Server 2016?

yes, it does. Thanks for the link. Cool feature is that it lets you right click the dump and launch a google search. That said, in my case, it doesn't indicate which driver caused it since it was ntoskrnl.exe that crashed.

I got a Blue Screen of Death on a Windows Server 2016 VM. The stop code was "Driver Corrupted Expool" Yesterday we added a couple drivers for a Xerox copier so that's the first thing that jumps to mind. I looked through event viewer and didn't see anything leading up to the crash. It's odd because it happened at 7:45 AM, long after the backup jobs finished, and before most of the users had arrived. Is there a free utility like whocrashed that will tell which driver BSODed the server?

I'm a little confused. You want a batch file to call a powershell script that generates an email with the date inserted in to it?

Can you do what you do for under $20 per phone? (or under $30 after taxes) Can you do that without a long term contract?

nice to see it's back.

@scottalanmiller said in cost of the whitebox:

That wasn't the issue here, though. This issue was: user modified a working machine in a way that didn't work and user lied or withheld the critical troubleshooting information to drive up the cost.

True. The only thing I could say is that with Dell/HP, we can look up the original build.