@scottalanmiller said in Random Thread - Anything Goes:

@nadnerb said in Random Thread - Anything Goes:

.... and not knowing the scale or legend and the map isn't to scale.

LoL

I did a gig in L.A. Things "looked" close together so we (wife + 3 kids) didn't rent a van just Uber. Would have been cheaper to rent the van.

We did do a lot of walking. We were the only ones on the sidewalks. Peeps in cars looked at us like we were from outer space.

Being from Edmonton, it was tough to get used to the polluted air.

Patrick King interviews.

https://www.bitchute.com/video/euMT6jUwXhym/

https://odysee.com/@LauraLynnTT:9/PatKing---04-August-2021_PatKing_SOLO:6

Looks like his case blew the doors off our province's "extraneous measures". All were removed last week with the official announcement this morning.

@nadnerb said in Random Thread - Anything Goes:

The ring sitting on the counter is for a wok. That's actually not a bad idea.

Stir Fry. Mmmm Deeeliscious!

@dashrender said in Windows images - ACHI or RAID/RST?:

@scottalanmiller said in Windows images - ACHI or RAID/RST?:

@dashrender said in Windows images - ACHI or RAID/RST?:

@dustinb3403 said in Windows images - ACHI or RAID/RST?:

@dashrender

@dashrender said in Windows images - ACHI or RAID/RST?:

then MS needs to include the RST driver in their images.

From you bringing it into the conversation. This isn't on Microsoft to include, this is on the hardware vendor to include.

Not really - MS includes most of the in use drivers these days - they started including Dell and HP RAID drivers for example.

That's really neither here nor there.

LOL- but if Intel/Dell and whatever other OEM's (I've read Asus is doing the same thing as Dell - RST by default) then they (Intel, etc) will need to get MS to include the RST driver.

It's up to the product vendor to run through the HLK certification process among a few other steps prior to Microsoft approving the driver for distirubtion from within the OS.

This is not a Microsoft thing. This is an OEM/ODM thing with Dell being the offending OEM at this time.

@dashrender said in Windows images - ACHI or RAID/RST?:

@phlipelder said in Windows images - ACHI or RAID/RST?:

@dashrender It's not Microsoft that did this. It's Dell's imaging team that set up the default firmware settings and imaged based on that. They then SysPrep'd the OS for OOBE (Out of the Box Experience).

Yeah - I know that, or at least assumed that. I'm wondering if there's any agreement between Dell and Intel requiring this type of setup on these processors.

We pull the whatever drive that comes in the Dell units we sell and install an Intel NVMe drive.

All of them get set up with an OS image that we have for each of our clients.

The BIOS settings get corrected at that time to AHCI.

@dashrender It's not Microsoft that did this. It's Dell's imaging team that set up the default firmware settings and imaged based on that. They then SysPrep'd the OS for OOBE (Out of the Box Experience).

@dashrender said in Windows images - ACHI or RAID/RST?:

LOL - I love it

reply 1 - leave it alone, use their driver
reply 2 - flip it, use normal AHCI driver.

Thanks guys.

Yup. Could get religious. ;0)

Reason for flipping it: Single drive no RAID.

Someone royally screwed the pooch in imaging on this one IMNSHO.

@dashrender said in Windows images - ACHI or RAID/RST?:

It appears that Dell is now shipping their xx20 series laptops with RAID enabled in the BIOS instead of ACHI.

As such, I've found some threads where people were trying to get the drivers - and they are using the Intel RST drivers (FakeRAID drivers).

I'm curious about anyone's thoughts on this here?

Additionally - a few noted that their newer Dells would revert to RAID if they switched to ACHI - causing the systems to BSOD on boot and a call to IT to "fix it" i.e. switch it back.

https://www.dell.com/community/Optiplex-Desktops/Convert-from-RAID-Bios-Setting-to-AHCI-Bios-setting-without/td-p/7379330

There's links in the above. Flip it.

@gjacobse Set up the Hyper-V host from scratch about 60-75 minutes up to date.

Set up the required base OS virtual machines about 45-60 minutes (count does not matter).

Greenfield Active Directory, OUs, GPOs, DNS, DHCP, Folders, and Shares about 45-60 minutes.

Import and configuration of base GPOs about 60 minutes.

Exchange on-premises about 30 minutes post Exchange install.

Script to set up users, their groups, and their mailbox about 60 minutes.

Time to run the script: 60 seconds.

Done.

User count does not matter. All in PowerShell.

And yes, all of our clients are on-premises Exchange.

EDIT: We charge a flat fee for the above.

@eleceng Pic the server setup with the cover open, the motherboard, the motherboard's make and model, and the power supply make and model.

We've been building servers for eons. We may have a compatible PSU sitting in our bin or at least be able to indicate what to get from auction site(s).

As far as activation goes, does Safe Mode work?

EDIT: Boot the VM to Server 2003 .ISO --> Recover --> CMD --> slgmr /rearm [ENTER].

@travisdh1 said in Random Thread - Anything Goes:

@phlipelder said in Random Thread - Anything Goes:

@nadnerb said in Random Thread - Anything Goes:

Ouch ... that brought back a painful memory.

ATI Rage Fury MAXX

(Image Credit: Internet)

We had a client with a fair number of very proficient Photoshop drivers. They needed way more GPU than the then current "best" could give them.

So, we built a bleeding edge system with this card.

Everything seemed to pan out but then the drivers came back and bit us in the arse.

Ultimately, a very expensive failed experiment.

Remember the All-In-Wonder cards? I had one of those a long time that I used as a DVR. Same deal, but multiplied by 2 because of the TV tuner.

Yup. Lots of horror stories around ATI and their dismal driver record.

We just went through a round of pain with AMD/ATI RADEON PRO W5700 series cards flaking out in SolidWorks/3D CAD situations.

As much as things change, they sure remain the same.

@nadnerb said in Random Thread - Anything Goes:

Ouch ... that brought back a painful memory.

ATI Rage Fury MAXX

(Image Credit: Internet)

We had a client with a fair number of very proficient Photoshop drivers. They needed way more GPU than the then current "best" could give them.

So, we built a bleeding edge system with this card.

Everything seemed to pan out but then the drivers came back and bit us in the arse.

Ultimately, a very expensive failed experiment.

@stuartjordan We have an aggregator that puts it together for us:

We are net importing energy because it costs more in CO2 taxes to run our coal plants.

EDIT: Forgot the link: https://twitter.com/ReliableAB/status/1393228855733805056

@nadnerb said in Random Thread - Anything Goes:

@IRJ

Reminds me of the times where a system drive would crash, we'd get the call, I'd show up, and low and behold a rare earth magnet was holding their entire kitten p*rn collection to the side of the PC right near the drive's location.

Heh ... those were the days.

@syko24 said in Who's sharing that printer?:

@mr-jones said in Who's sharing that printer?:

I'm wondering if anyone knows a solid way to track down who is sharing a network printer in a Windows environment?

I have all network printers deployed via GP, and per OU as appropriate, but I'm seeing someone else has shared one, and renamed it something outside of my naming convention. I'm trying to track down which client has done so. I'm currently digging around, but I'm not finding anything.

Any ideas?

Not sure if this is what you are looking for but you can use Advanced IP Scanner and run a network scan. If a system has any shares it will list them below system name/ip address.

https://www.advanced-ip-scanner.com/

Excellent utility. We use it to map IP to device name. I haven't taken a deeper look at its abilities. So, great one!

@mr-jones The shared printer should have a machine name associated with it? Grey matter isn't firing on all cylinders yet ...

Connect to that printer and check the Advanced properties to see what the name of the host is.

This one could be a tough one.

Problem: One network blip and the intranet clients will lose their ability to resolve internal DNS A records for whatever the TTL setting is for them. BTDT

Public DNS servers do not belong anywhere near your intranet setup.

I.E. don't have DNS0 192.168.33.5 DC/DNS and DNS1 8.8.8.8 or whatever public DNS server. Bad. Just. Bad.

There are two ways to solve this that won't cause you grief:

• Set up as you are but leave DHCP off on the secondary device
• Set up DHCP Failover via a second DC

The second option can be licensed via your favourite SPLA provider for very little cost per month over purchasing a full license.

@JasGot Probably has young kids.

@brandon220 said in Browsing shares from W10 (2004) on a domain:

Started having trouble with Win10 (2004) seeing local shares on the network recently. Computers randomly show up in "Network". The proper services are enabled and running per MS documentation:
Function Discovery Resource Publication
Function Discovery Resource Publication
SSDP Discovery
UPnP

Firewall is set properly but it doesn't work even if you disable the FW temporarily.

Network Discovery is enabled, and of course the network is private as it is on a domain. It should work without enabling SMB 1.0/CIFS. Users can connect to shares by entering \servername in the file explorer with no issues.

At this point it may be easier to add a startup script that maps the shared drives. Problem is - the users are so used to browsing to the resource they need manually via the 'network' section within explorer.

Thoughts?

Receive Segment Coalescing (RSC). Disable that on your file server's pNIC/vNIC and on the desktop/laptop adapters(s) that support it.

@PhlipElder Y'all see the "Great Reset" push that's coming down the pipe?

Do all y'all understand, and I mean understand, what it is implying and what it means for the regular Joes & Janes of this world?!?

My family has been through two Red Revolutions and one near miss with the Armenian Genocide. The whole thing is just too coincidental.

Sorry, not buying it. I'm not buying the virus push at all anymore.

I'm firmly in the Better Dead Than Red camp here.