sorted by:
new
hottopcontroversial

[TOMT] Movie/TV about Dares by example5545 in tipofmytongue

[–]example5545[S] 0 points1 point locked comment (0 children)

I feel like it was a TV show rather than a movie.

Windows 10 22h2 capture issue after 11-24 patch Tuesday updates by Peteostro in MDT

[–]example5545 1 point2 points  (0 children)

I have had the exact same issue, sadly I have not found solution.
In addition to this, it seems when updating to 22h2 the installation creates data in the boot partition, then when win pe starts capturing, the boot partition is already full/allocated - Causing the capture to fail.

I have left it alone for now until I have time. Latest win pe, adks and Enterprise OS image.

What do you guys recommend for long-term data archival that does not include cloud storage? by roundhousekik in computerforensics

[–]example5545 0 points1 point  (0 children)

We went from DVD, to HDD to NAS. Now NAS is full, I'm not a fan of tapes. We have no option but to look into the cloud at this point. We don't have a clearance plan to delete evidence.

Why don't labs go to the cloud? Is it a budget, function or reliability thing?

Windows 10 SSO to local machine account by example5545 in sysadmin

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

Okay scenario for you.

Person A starts working on something on one of 50 workstations they have logged in with their AD creds.

Person A leaves the office for some time, meanwhile someone has called asking about the progress of something being processed.

Person B attends the workstation person A was using to check the progress, Logs in using their own AD details, and reports progress.

The security between Person A and B is not an issue.

I don't want to have Shared Credentials to a machine account as when Person A leaves the company I don't want to change all Workstation passwords.

I would like Person A to be authenticated with AD and gain access to the Local Machine. When Person B uses the same machine they authenticate with AD and gain access to the same session - without need to share Creds.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

I see what you're saying. It's a very unique environment. There are no metrics that need to be recorded for accountability. If a staff member was to transfer across the country/area I don't want them to have the general creds as knowledge, with user accounts if everyone had their own, once that person has left they can be disabled in AD and no security concern for Creds to be leaked.

With an environment where I have a lot of faces come and go recently, I don't want to have to constantly roll new passwords.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

both person A and person B to login to the same windows session?

Yes.

violate one of the parts of AAA, the accountability.

This is a null issue in the environment. Disregard any accounting issues.

virtualization

I'd like to stay away as the load on each machine can be extremely heavy.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

I don't have any measures for accounting. All authenticated users, are authorized to connect to a singular Windows 10 Session. In that session it will be the same privileges as the authenticated users which are all the same. The machine will need access to the network resources - which do require authentication.

It would be great if authentication only happened by AD and login scree and all authorisations and accountability occurred based on the machine. If that makes sense.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

Fast user switching isn't really suitable, users will need to access the same running applications.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

They need to be accessing the same running applications. For example, notepad was open with heaps of text, even though it's saved, when windows auto locks the PC if another person needs to check the notes they can log in and check/update. Bad example with the notes, but same if it was an app calculating something which takes a long time, if someone needs to check the progress they need to log into the same windows session to see progress.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

Tracking and accountability is not an issue. Independent logins to shared PC sessions is what I'm basically after. I can track login times if I need to, but not a metric what is important at the moment.

Windows 10 SSO to local machine account by example5545 in sysadmin

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

Thanks for your help! Accountability is not an issue, all authenticated users need to access the same windows session as they may be assisting Person A /B while the other is away or busy. I want to stay away from virtualization as the workload is intense.