Posts made by jt1001001

@dafyre Bitwarden has been great here we migrated the whole company over to using it and forced password changes on the coupel external sites we control. So far no issues.

@scottalanmiller that was Cortland Beer Co. We have stopped at Ithaca before but not on this trip

Exploring g the Cortland,NY area. Found beer

Office Desk at the new job, Dilbert riding shotgun today

@scottalanmiller Dilbert's proving level 2 today:

Flying "solo" today at the new job, so much to learn still.

@smartfiber Sent you a DM

@smartfiber I sent you a DM

@scottalanmiller We were out of the area when we heard. Know that location. So far the news is not good and our kids are asking about it. Sad day here.

@BraswellJay I normally do not promote however good friend of mine (and former co-worker) demo's some headphones for Ingram and he liked the Jabra Evolve 2 85 for dual ear protection. I tried them and found they worked well but may be a bit heavy for all day wear.
Here is his video demo of a few different headsets.
Youtube Video

@gjacobse winlink's still around? we took our relay down what 9-10 years ago maybe? I may have to try and get it re-set up.

@brandon220 we are currently on Hyper-v for 2 VM's (and one physical DC that bit the bucket, see my other posts) I'm interested in Proxmox as well to replace Hyper-V as we do have one silly need for 1 or 2 on prem servers (more for development/testing and provisioning phones than anything) so keep us posted

@Dashrender I'll be finding out next week.

admittedly, our deployment will be more "seat of the pants' as we had a DC failure and I'm the new guy so make him do it. I haven't even looked at all the potential issues and pitfalls. I just know that for a company of our size (less than 100 users, workforce now primarily remote) a central active directory structure is not necessary nor needed. We aren't doing LDAP/ADFS/SAML anywhere today. Heck we don't know yet if we even need MDM (Intune) but if the higher ups are allowing up to get licenses might as well play with it.

@Dashrender do they need local admin rights? For us the answer is NO.
Right now I'm working on an image for our systems with apps re-installed and Chocolaty for future package management. A local admin user with password known to IT (different foe each machine) is created, and I-T person adds machine to Azure AD though Accounts section of Win 10 (with pre-set password). Reboot, new user logs in and is prompted to change their password. Will simplify this as time goes on but its a good start.

@scottalanmiller as I found in our case, AD here was adding absolutes 0% while actually creating more of an administrative headache. 99% of our applications here are "in the cloud" (unlike my old company) and all the DC was doing was print, some file shares, and 1 or 2 group policies (that weren't even working right!). So moving to Teams (see post in other discussion) will alleviate the file share; may build a linux file server for 1 or 2 use cases where Teams/Sharepoint won't work. Group policies are unnecessary and worst case we can upgrade our licenses and go Azure AD/Intune if we need to. Printing, well its printing and it sucks but we'll figure it out. Best is the CTO and President are on board without so much as a blink.

@Dashrender That's what I have to play with as I'm not sure at the channel level how permission inheritance works

New job has me swamped. Going to get rid of Active Directory as one of the dc suffered a failure this week and executive management said "been meaning to do that for a while. You take the the project. What licenses do you need". No questions, not push back, just OK get it done. Good to work in a company where pretty much everyone is at least somewhat technical.

@gjacobse I am lucky that the new company rarely has to fax (though we often have to set up for customers) so glad to have dodged that bullet.

@Dashrender I am about to set up our corporate Teams as the mess I came into is, well, a mess. We've decided to essentially blow it all away, lock it down so users can't create teams on their own (yes, aware that Microsoft does not recommend this), and to use our org chart and set up Teams that way. So each part of the org chart (Finance/accounting, Sales, Operations, Order Management, Support, Marketing, Executive in our case) is getting its own team. Areas where we need inter-org collaboration (Such as our provision group which involves sales, operations and support) will also get its own team. All told there will be I think 15 teams the way I have stuff laid out. We're going to try it out for 30 days and see how it goes, tweak from there. One suggestion someone made is for the inter-op teams to be a channel intead; off one of the main org chart teams; not sure how well that will work.

@WrCombs yeah I need that