Trend Micro WFSB NEVER EVER EVER EVER EVER EVER
We took on a new client with an install of this stuck on their DC. I managed to clean it out last night but got a bit of a morale boost when I found out this installation was from not the previous IT support, but the one before them! Score one for us actually getting rid of moldy AV instead of leaving it there
Who can I sub contract my HP calls to?
Sent from my Pixel using Tapatalk
Your posting is medium, its not rare and its not well done
- Krans 26/7/12
Last migration I was on site for we had issues with DHCP not working through a sonicwall between two subnets, apparently you have to set up specific DHCP relays even if you have an allow all rule in place between interfaces but because I had my linux laptop with me I could use a script built into nmap to detect dhcp status on the network. Closest thing I could find on windows would have again been nmap or dhcploc, but neither are built into windows! HAH!
Viking, n.:
1. Daring Scandinavian seafarers, explorers, adventurers, entrepreneurs world-famous for their aggressive, nautical import business, highly leveraged takeovers and blue eyes.
2. Bloodthirsty sea pirates who ravaged northern Europe beginning in the 9th century.
Hagar's note: The first definition is much preferred; the second is used only by malcontents, the envious, and disgruntled owners of waterfront property.
Wmi was indeed reset.. As was kicking the machine from sccm and letting it reconfigure..
Which setting are you referring to? (also probably yes saying as we have 122 desktops with no issues)
Originally Posted by lubica
Today I did a good thing.. I looked at the new vmware environment I inherited and immediately started fixing it.. We are now no longer running out of space.. I just wish we didn't have standard because drs would be awesome.
Originally Posted by lubica
Viking, n.:
1. Daring Scandinavian seafarers, explorers, adventurers, entrepreneurs world-famous for their aggressive, nautical import business, highly leveraged takeovers and blue eyes.
2. Bloodthirsty sea pirates who ravaged northern Europe beginning in the 9th century.
Hagar's note: The first definition is much preferred; the second is used only by malcontents, the envious, and disgruntled owners of waterfront property.
Today in SCCM fuckery:
- i'm now using collection variables to decide which image is deployed and which domain is joined.
The correct image is deployed to rooms, hooray.
The computers are joining the student domain correctly - variables being correctly parsed as per smsts.log. Sadly, once they have joined the student domain, no students can log in as they have picked up the staff domain security policy, which blocks students from logging in.
wonderful.
Please don't teach me what to do with my pc.
Viking, n.:
1. Daring Scandinavian seafarers, explorers, adventurers, entrepreneurs world-famous for their aggressive, nautical import business, highly leveraged takeovers and blue eyes.
2. Bloodthirsty sea pirates who ravaged northern Europe beginning in the 9th century.
Hagar's note: The first definition is much preferred; the second is used only by malcontents, the envious, and disgruntled owners of waterfront property.
i think the bod who made the image had it on one domain and fucked it.
luckily it's only win7, office, adobe CC + visual studio so shouldn't take long to re build from scratch.
not.
ran into a fun "machines not being authorised" earlier in the week too. it turns out one of our new college's student domain is in a separate forest so the one site server on their office was refusing to service clients. Working as intended but just another spanner i'd never seen before.
Please don't teach me what to do with my pc.
you ain't seen fucking nothing yet when it comes to cross forest shenanigans.
my previous employer is a large defence contractor, as i have hinted at in the past and their entire setup is separate domain forests with cross forest trusts and firm firewalls between the forests, the complexity involved takes a diagram to sort out and the whole thing is tied together with federation services, it also produces an amazing number of problems.
say you have two users, in the same office lets call them Sam and Ben, both are project manglers and now Ben calls in with a login issue, only where's the fucking problem ? is it the domain his workstation is on ? is it because he's been a fucking numpty and plugged the wrong drive into the wrong chassis ? is it his actual user account ? or is he forgetting to tell you that he's actually using the citrix cluster sitting on another forest entirely because the performance there is miles ahead of the shitty workstation he's issued with ? or maybe it's the application he's running, that's sitting on a app server on yet another domain forest ? or maybe the actual problem is that the SQL server backing said app server, that sits on YET ANOTHER forest is fucked.
you could just have a look at Sam's setup, but there is no guarantee his actual setup is even remotely similar to Ben's, he might be using a thin client directly into the Citrix cluster instead and you cannot easily troubleshoot across the domains even as a sysadmin, because there is no assurance you even have access to even a third of the junk the user interacts with, and even if you did you can't easily trace problems from the workstation level trough the domain stacks because everything is rigidly firewalled, but poorly documented.
i am so happy i worked in my own little "sandpit" with a subsection of regular users, at least some degree of order could be imposed on the shit i could touch, though i readily admit i spend half my time pulling down overly engineered solutions and smacking in "primitive" "by the book" solutions, oddly enough uptime increased and breakdowns decreased at a regular phase until i quit, of course now the whole thing is just rolling along, basically unmanaged because hiring replacements is hard, even with a fucking 6 month lead time on the resignation.
on the up-side, they haven't had a unrecoverable and ungooglable problem yet, something i am rather proud of, considering that was the fucking norm before i started.
Last edited by Liare; July 13 2017 at 12:26:02 PM.
Viking, n.:
1. Daring Scandinavian seafarers, explorers, adventurers, entrepreneurs world-famous for their aggressive, nautical import business, highly leveraged takeovers and blue eyes.
2. Bloodthirsty sea pirates who ravaged northern Europe beginning in the 9th century.
Hagar's note: The first definition is much preferred; the second is used only by malcontents, the envious, and disgruntled owners of waterfront property.
Because I just hunted down a "lost" email: fuck MTAs that don't respect the Prio setting of MX records
Bookmarks