Posts made by bbigford

Edited original content to reflect an optional phase of the projects... just burn it, salt the land, and start a new.

@scottalanmiller said in Certifications in the toilet:

No comments about the terrible keyboard and mouse?

Is that a desktop being used asa server?

I hate to ask what the big black box in the corner is.

Not sure what the desktop does yet... Haven't yet flown to California to check it out (coming weeks, these are just pics from the onsite contact). The black box appears to be a filing cabinet if I zoom in. Because it's next to a drain, and sitting on the floor, it's probably important.

@scottalanmiller said in Certifications in the toilet:

@irj said in Certifications in the toilet:

Good thing toilets never back up...

Neither do those servers!

Actually... I need to edit my content. They don't have backups, and never have. Ever. They do use "Previous Versions" aka volume shadow copies; which of course are NOT backups. They should know... because when they got hit with cryptoware last year, the first thing the infection did was -you guessed it- delete their shadow copies.

@bbigford said in CredSSP and RDP in Windows 10:

@scottalanmiller said in CredSSP and RDP in Windows 10:

@bbigford said in CredSSP and RDP in Windows 10:

Just went through a work thread on this last night. So annoying.

Yeah, a little heads up on this would have solved a lot of things.

Windows 10 - 1709 update ends in xxxx717 if you want to uninstall it on an as-needed basis on desktops (for anything running Home and doesn't have secpol available, or domain joined for the same reason).

Windows 10 - 1803 ends in xxx721.... they all hit on 05/09/18 (my Win10 Pro laptop had that this morning and gave me issues after a reboot... didn't want to modify my local policy but instead just uninstalled and rebooted).

Also @scottalanmiller , I used this downloadable tool to hide the x721 update for 1803, before uninstalling and rebooting. It had auto-installed later that day.

We took on a larger account a few years back. The setup was pretty awful. Changed some things along the way, and now we're at the point of redesigning some big moving parts.

Fast forward to 6 months ago, the company we took on consisted of originally 3 guys who broke off from another company, became successful in the same industry, and turned around to buy the company they came from. 2 months ago I told them we should absorb that account, so we did.

That company's network is... gross; to say the least. it's much smaller, but far worse. The previous provider (part owner of the MSP) has a certification list with some pretty good looking certs: CCNA, MCSE (security, messaging), MCSA, etc.

He originally built this network... in the bathroom. I asked the client about other space we could construct, to which I'm told, "oh yeah, we do lots of add-ons and construction. We could put together a very nice 12' x 12' communications closet just above that ceiling on the second level no problem. It can have AC, ventilation, filtration, power. Anything you need just let us know."

All that comes to mind from the below photo is, "Hurry up in the bathroom, man! The network is down! I need to get in there!" You probably should use the provided keyboard with rubber gloves, because of all the shit particles that are floating around.

I won't go into the laundry list of stuff they have wrong... but some of the highlights are no backups (zero. Never existed. Ever. Only ever had volume shadow copies, aka "previous versions"... which they know aren't backups after they got hit with cryptoware last year and all their shadow copies were deleted) outdated ESXi, everyone remotes into a terminal server (even though they are onsite with desktops and don't need to for any reason), repurposed Linksys WRT54G for internal wireless, ISP fixed wireless with very low throughput and heavily susceptible to rain fade, appears some Cat3 cable in places, UPS' that were discontinued almost a decade ago (not released to market... discontinued), some desktops ranging to 15 years old.

Phase 1: Gut and redesign the systems/network (wearing rubber gloves when touching... anything).

Phase 2: Move the communications closet and get a new ISP (new ISP already scoped out; also wearing gloves).

Optional Phase: Burn it. Salt the land.

@scottalanmiller said in CredSSP and RDP in Windows 10:

@bbigford said in CredSSP and RDP in Windows 10:

Just went through a work thread on this last night. So annoying.

Yeah, a little heads up on this would have solved a lot of things.

Windows 10 - 1709 update ends in xxxx717 if you want to uninstall it on an as-needed basis on desktops (for anything running Home and doesn't have secpol available, or domain joined for the same reason).

Windows 10 - 1803 ends in xxx721.... they all hit on 05/09/18 (my Win10 Pro laptop had that this morning and gave me issues after a reboot... didn't want to modify my local policy but instead just uninstalled and rebooted).

Just went through a work thread on this last night. So annoying.

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

While in an Office 365 PowerShell session, anyone know what the 'name' value refers to? I think what a client did was simply rename an account when someone quit, and here is the result.

Amanda quits, backfilled by Jane. Display name, UPN, SAM, alias, everything shows as Jane, except 'name'. Going through Exchange mailbox and MSO user properties via the GUI, no trace of the word 'Amanda' anywhere.

Anyone know what that value actually refers to? Before today I thought it was probably UPN, until today I saw there is a separate value for UPN.

Can you show an example?

That's the SamAccountName attribute that cannot be changed.

You were correct after I double-checked. What I find odd though, is the samAccountName doesn't show as emilyr, it shows as emily59172-558041006 ... where does it even pull emilyr from do you think?

Edit: I've tried marking this as solved, but can't find an option for that.

Have @scottalanmiller do it.

Ah, I'm guessing that is not a function everyone has the ability to use I'm guessing.

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

While in an Office 365 PowerShell session, anyone know what the 'name' value refers to? I think what a client did was simply rename an account when someone quit, and here is the result.

Amanda quits, backfilled by Jane. Display name, UPN, SAM, alias, everything shows as Jane, except 'name'. Going through Exchange mailbox and MSO user properties via the GUI, no trace of the word 'Amanda' anywhere.

Anyone know what that value actually refers to? Before today I thought it was probably UPN, until today I saw there is a separate value for UPN.

Can you show an example?

That's the SamAccountName attribute that cannot be changed.

You were correct after I double-checked. What I find odd though, is the samAccountName doesn't show as emilyr, it shows as emily59172-558041006 ... where does it even pull emilyr from do you think?

Edit: I've tried marking this as solved, but can't find an option for that.

@nerdydad said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

While in an Office 365 PowerShell session, anyone know what the 'name' value refers to? I think what a client did was simply rename an account when someone quit, and here is the result.

Amanda quits, backfilled by Jane. Display name, UPN, SAM, alias, everything shows as Jane, except 'name'. Going through Exchange mailbox and MSO user properties via the GUI, no trace of the word 'Amanda' anywhere.

Anyone know what that value actually refers to? Before today I thought it was probably UPN, until today I saw there is a separate value for UPN.

Can you show an example?

That is the original user that occupied that account. Unfortunately, when DisplayNames are created, they cannot be altered. Of course, this company is doing it wrong anyways because the old user's account should be disabled and deleted after a while. New employees should be created new AD accounts. If the new employee needs something from the old employees account then the new employee should be granted access to the old employees mailbox.

The Display Name in this case would be Catalina M, it's showing correctly in the second picture...

@dbeato said in Office 365 PowerShell question:

@bbigford said in Office 365 PowerShell question:

While in an Office 365 PowerShell session, anyone know what the 'name' value refers to? I think what a client did was simply rename an account when someone quit, and here is the result.

Amanda quits, backfilled by Jane. Display name, UPN, SAM, alias, everything shows as Jane, except 'name'. Going through Exchange mailbox and MSO user properties via the GUI, no trace of the word 'Amanda' anywhere.

Anyone know what that value actually refers to? Before today I thought it was probably UPN, until today I saw there is a separate value for UPN.

Can you show an example?

While in an Office 365 PowerShell session, anyone know what the 'name' value refers to? I think what a client did was simply rename an account when someone quit, and here is the result.

Amanda quits, backfilled by Jane. Display name, UPN, SAM, alias, everything shows as Jane, except 'name'. Going through Exchange mailbox and MSO user properties via the GUI, no trace of the word 'Amanda' anywhere.

Anyone know what that value actually refers to? Before today I thought it was probably UPN, until today I saw there is a separate value for UPN.

@scottalanmiller said in How long to keep people's AD/Exchange accounts:

@kelly said in How long to keep people's AD/Exchange accounts:

@momurda said in How long to keep people's AD/Exchange accounts:

Just had to lookup what catfacts is.

https://sendcatfacts.com/

Someone needs to make sendcatfax.com too!

Random, literally still faxing, cat pics to random numbers on a dialer.

"Install nano because I prefer it over vi"

Nano really should just be the standard at this point, IMO.

@scottalanmiller said in Mapping OneDrive Business to a drive letter:

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@brrabill said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@scottalanmiller said in Mapping OneDrive Business to a drive letter:

@momurda said in Mapping OneDrive Business to a drive letter:

What is the point of OneDrive if you cant mount it as a drive letter easily?
Someone please explain. It seems absoultely horrible.

Why woudl you want it as a drive letter? The drive letter is an old holdover that isn't very good. You can mount OneDrive as a folder which is better most of the time.

Assuming that OneDrive syncing actually works, which generally it is pretty poor.

I find OneDrive itself (the consumer one) works great.

ODfB, though ... LOOKOUT!

Hah, yeah that's the one I was speaking toward. Assumed that is what is being brought up here since it's for a business. I could be wrong though.

But yeah, ODfB... wow. I hear it's a little better but I've completely written it off as of late.

Besides Scott's problems, what issues are yall talking about? Honestly, we have had very little issues with Exchange Online and SharePoint Online over the course of 2-3 years.

Referring to OneDrive for Business syncing. Outside of SharePoint Online, speaking only to the ODfB syncing; it'll often just break for no apparent reason and stop syncing to workstations.

Not really concerned with syncing, but wanting to use it similarly to a networked drive on a hosted server instead of an on-prem server.

WebDAV. Acts just like any mapped drive.

That's what I started thinking, but that isn't focusing on OD/ODfB; that goes beyond a single client and focuses on central delivery. Used it for uploading/downloading unsupported file types in regards to SharePoint; couldn't upload to SharePoint, but WebDAV didn't balk.

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@brrabill said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@scottalanmiller said in Mapping OneDrive Business to a drive letter:

@momurda said in Mapping OneDrive Business to a drive letter:

What is the point of OneDrive if you cant mount it as a drive letter easily?
Someone please explain. It seems absoultely horrible.

Why woudl you want it as a drive letter? The drive letter is an old holdover that isn't very good. You can mount OneDrive as a folder which is better most of the time.

Assuming that OneDrive syncing actually works, which generally it is pretty poor.

I find OneDrive itself (the consumer one) works great.

ODfB, though ... LOOKOUT!

Hah, yeah that's the one I was speaking toward. Assumed that is what is being brought up here since it's for a business. I could be wrong though.

But yeah, ODfB... wow. I hear it's a little better but I've completely written it off as of late.

Besides Scott's problems, what issues are yall talking about? Honestly, we have had very little issues with Exchange Online and SharePoint Online over the course of 2-3 years.

Referring to OneDrive for Business syncing. Outside of SharePoint Online, speaking only to the ODfB syncing; it'll often just break for no apparent reason and stop syncing to workstations.

Not really concerned with syncing, but wanting to use it similarly to a networked drive on a hosted server instead of an on-prem server.

Networked? Are you referring to WebDAV shares for a backend way to quickly access content, or do you actually mean OneDrive...?

@wls-itguy said in VMWare vSphere 6.5 loses licensing:

@bbigford said in VMWare vSphere 6.5 loses licensing:

@wls-itguy said in VMWare vSphere 6.5 loses licensing:

@bbigford said in VMWare vSphere 6.5 loses licensing:

@wls-itguy said in VMWare vSphere 6.5 loses licensing:

Anyone else have this happen recently? I got Veeam backup failure notifications last night and this morning saying that the servers being backed up were disconnected. I connected to vCenter and Sho'Nuff two of my hosts were disconnected. When I tried to reconnect it said I didn't have licensing. It took a bit but I finally got them reconnected and relicensed.

Haven't provided enough information, but here's why ours get relicensed often...

If you're a VMware partner, you get access to their Enterprise Plus licensing. That's very expensive licensing that they just hand over. But it also means that we have to go through quarterly and reapply licensing; VMware sends it to us, and we replace it.

Can you provide some more information about your licensing level, etc?

Essentials Plus.

Does the license actually disappear, or does it just show that it is not applied to any hosts but the license is still in the console?

Not applied to any hosts. But when I finally got into it I couldn’t assign them. It was like they were stuck. Had to reboot the center appliance and then I could assign and then I could reconnect.

Sounds like your VCSA is jacked up (you're using VCSA, right? Not vCenter on Windows...)

I've had plenty of issues with VCSA 6.0, but none really with VCSA 6.5... In either case, just rebuild the appliance to see if that is the issue. Takes like 15 minutes.

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@brrabill said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@scottalanmiller said in Mapping OneDrive Business to a drive letter:

@momurda said in Mapping OneDrive Business to a drive letter:

What is the point of OneDrive if you cant mount it as a drive letter easily?
Someone please explain. It seems absoultely horrible.

Why woudl you want it as a drive letter? The drive letter is an old holdover that isn't very good. You can mount OneDrive as a folder which is better most of the time.

Assuming that OneDrive syncing actually works, which generally it is pretty poor.

I find OneDrive itself (the consumer one) works great.

ODfB, though ... LOOKOUT!

Hah, yeah that's the one I was speaking toward. Assumed that is what is being brought up here since it's for a business. I could be wrong though.

But yeah, ODfB... wow. I hear it's a little better but I've completely written it off as of late.

Besides Scott's problems, what issues are yall talking about? Honestly, we have had very little issues with Exchange Online and SharePoint Online over the course of 2-3 years.

As far as Exchange/SharePoint Online services, they have been fine for all of our clients.

@nerdydad said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@brrabill said in Mapping OneDrive Business to a drive letter:

@bbigford said in Mapping OneDrive Business to a drive letter:

@scottalanmiller said in Mapping OneDrive Business to a drive letter:

@momurda said in Mapping OneDrive Business to a drive letter:

What is the point of OneDrive if you cant mount it as a drive letter easily?
Someone please explain. It seems absoultely horrible.

Why woudl you want it as a drive letter? The drive letter is an old holdover that isn't very good. You can mount OneDrive as a folder which is better most of the time.

Assuming that OneDrive syncing actually works, which generally it is pretty poor.

I find OneDrive itself (the consumer one) works great.

ODfB, though ... LOOKOUT!

Hah, yeah that's the one I was speaking toward. Assumed that is what is being brought up here since it's for a business. I could be wrong though.

But yeah, ODfB... wow. I hear it's a little better but I've completely written it off as of late.

Besides Scott's problems, what issues are yall talking about? Honestly, we have had very little issues with Exchange Online and SharePoint Online over the course of 2-3 years.

Referring to OneDrive for Business syncing. Outside of SharePoint Online, speaking only to the ODfB syncing; it'll often just break for no apparent reason and stop syncing to workstations.