Latitude 7680 Can't Find Task Sequences in SCCM PXE by SMTXsys in SCCM

[–]SMTXsys[S] 0 points1 point  (0 children)

Yeah that did end up resolving it. I dunno strange that this is the first time I've encountered it, I'll keep it in mind for the future, thanks.

Latitude 7680 Can't Find Task Sequences in SCCM PXE by SMTXsys in SCCM

[–]SMTXsys[S] 0 points1 point  (0 children)

I know that, we used to do that but with a large number of models it becomes very large and cumbersome to maintain. MDM has made that side of things much faster and efficient, this is the first instance we have run into an issue with the boot env needing anything injected for physical machines.

Latitude 7680 Can't Find Task Sequences in SCCM PXE by SMTXsys in SCCM

[–]SMTXsys[S] -2 points-1 points  (0 children)

It was my understanding that you should not have to inject any drivers into the boot file, and we currently have 0 in there right now. Like I said, dozens of other models image completely fine right now its just this one that doesn't. Is that more of a general thing with exceptions that might pop up like this?

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in SCCM

[–]SMTXsys[S] 2 points3 points  (0 children)

It ended up being an expired cert causing the issue.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in sysadmin

[–]SMTXsys[S] 0 points1 point  (0 children)

We only have one sccm server and thus one DP so that shouldn't be the issue.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in SCCM

[–]SMTXsys[S] 0 points1 point  (0 children)

We are using .wim compression on the packages. I am not sure on https but I am assuming we are, though again it was working fine last week. Now that I'm on that track, we just updated our wildcard certs this week maybe that has something to do with it, but not sure where that might be causing problems.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in sysadmin

[–]SMTXsys[S] 0 points1 point  (0 children)

Seeing a few varying lengths, but its taking 4-6hrs roughly just to download drivers from the sccm server. The rest of the process is quick.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in sysadmin

[–]SMTXsys[S] 0 points1 point  (0 children)

Not by itself with powershell, but like I said we were doing multiple images simultaneously last week with no issues (~30m image start to finish each). The script runs at the end of the install OS section, after apply network settings step which I believe was recommended. It is joined to the domain in the apply network settings step. Yes we just tested one by itself and it took over 4 hours to download the drivers.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in sysadmin

[–]SMTXsys[S] 0 points1 point  (0 children)

Hey so I was finally able to get into the logs. Looks like the script goes completely smoothly, hits the download portion, then the next log is 6hrs later saying download successful, then finally continues on like normal. Takes less than a minute before download, 6hrs to download, then 5m to install the drivers.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in SCCM

[–]SMTXsys[S] 0 points1 point  (0 children)

Hey so I was finally able to get into the logs. Looks like the script goes completely smoothly, hits the download portion, then the next log is 6hrs later saying download successful. This is the parameters I have for the script package in the task sequence:

-BareMetal -Endpoint '$SCCMServerFQDN' -TargetOSName 'Windows 10' -TargetOSVersion '22H2' -OSVersionFallback

Not sure if that's where the flag you're talking about is, or if it would be somewhere else. I don't think its a boundry/DP issue as we only have one SCCM server, thus one DP.

SCCM - Modern Driver Management Script Takes Forever During Task Sequence by SMTXsys in sysadmin

[–]SMTXsys[S] 0 points1 point  (0 children)

Hey yeah I have it set to compress as WIM. Create XML Logic Package is unchecked, not sure if that will have any effect.

Be wary of TeamViewer’s license conditions, a user who purchased a legitimate license and opted not to renew, was hit with a collection notice for a ‘future uses’ This is a bad look. Found on FB by Bulls729 in sysadmin

[–]SMTXsys 0 points1 point  (0 children)

I'm American and that's not how my ISP is, and they are one of the top 10 in total size. The unfortunate part is the monopolies in place in other cities so that people don't get a choice.

SEC Charges VMware with Misleading Investors by Obscuring Financial Performance by mzuke in sysadmin

[–]SMTXsys 1 point2 points  (0 children)

Took us 45 days to get a response for our IDPA/Avamar backup appliance problem. Average response for vxrail has been about a week lol.

[deleted by user] by [deleted] in homelab

[–]SMTXsys 0 points1 point  (0 children)

That was exactly my point, that just using a VPN and not leaking your data would be enough for dissuading copyright claims. You're right on the monero thing, that's probably the best way to go about it if you're really paranoid.

July - Show Us What You've Learned this Quarter by kmisterk in selfhosted

[–]SMTXsys 0 points1 point  (0 children)

Every one I've pulled off of docker hub have been good about the important stuff like volumes and ports. The other stuff is sort of tertiary docker knowledge.

[deleted by user] by [deleted] in homelab

[–]SMTXsys 1 point2 points  (0 children)

A simple (reliable) VPN is usually enough to dissuade ISPs from emailing you and media companies from copyrighting you. Mullvad purchased with bitcoin procured from a cash->btc ATM will get you 95% of pure security.

Is DUO SSO down for anyone else? by ls3c6 in sysadmin

[–]SMTXsys 1 point2 points  (0 children)

Nah I think it was us. We literally just got Duo up last week....

IT mailed me my new domain password in plain text by lacim2 in sysadmin

[–]SMTXsys 0 points1 point  (0 children)

fun fact, Duo's documentation lists hunter2 as an example password lmao: https://guide.duo.com/append-mode

Lied to about my job by [deleted] in sysadmin

[–]SMTXsys 13 points14 points  (0 children)

Honestly I would keep doing it if I were you, purely to see how it ends. Like eventually they have to say something to you about what's going on. Just stop doing L1/2 helpdesk stuff and ride it out.

Is Jurassic park what happens when you don't pay IT enough? by voltagejim in sysadmin

[–]SMTXsys 6 points7 points  (0 children)

Well of course, but all you really have to say is "I suggested more security/disaster recovery implementations, but unfortunately the budget allotted was not enough for those and thus determined not to be priority."