dcwhitworth

I've written some useful PowerShell script that I want my team to use for domain and O365 work, but I'm struggling to get anything to work for anyone else. There just seem to be too many hurdles to overcome, modules to load, logins, execution policies, not liking programs on network drives, certificates not working. I get it all working on my PC but then something different won't work on someone else's. Has anyone got any hints on sharing PowerShell scripts around a team ? How do you lessen the pain without (preferably) totally throwing away security ?

A Russian couple are walking through Red Square one evening. They feel a slight precipitation. "I think it’s raining," says the man. "No, it’s snowing," replies the woman. "How about we ask this Communist officer here? He is always right!" exclaims the man. "Officer Rudolph, is it raining or snowing?" "Definitely raining," Officer Rudolph replies before walking off. The man turns to his wife with a smile. “See? Rudolph the Red knows rain, dear.”

It worked OK for us as a homework hand in area, provided the students dragged and dropped files into it rather than trying to directly save them there.

Beware of one thing, the permissions can be set up but they may interfere with some software. PowerPoint (the only one I definitely recall) for instance, creates and deletes some temporary files as part of the saving process. If the user has create but no delete rights the save will fail as the temp files can't be removed by the user. Or at least that's how it used to work some years ago when we had something similar set up as a homework hand in area.

Hmmm, that seems to work but it only shows me domain local groups on the other domain. Edit - which are the only groups that groups from a trusted domain can be added to. Ho hum, seems my old domain is not well set up for this.

Morning all, We're in the process of migrating between a 2012 domain and a 2016 one, we've got a trust set up between them and I want to enable users on the new domain to access files on the old one. It's a long, long while since I last used a domain trust (server 2000 was involved I think) so I'm hazy about how to use it, if my memories of that time are even relevant any more. I thought I could simply add groups from the new domain into groups on the existing domain and thus automatically delegate them the same rights, but when I try to do this in ADUC the new domain doesn't appear in the locations list when I click on 'add'. The only route I can seem to find is to go to the existing directories and shares and add the new groups with the same rights as the old ones, which seems like a hugely laborious and error-prone process, I'm left thinking there must be a better way and that I must have missed something. Can anyone enlighten me, or alternatively crush my hopes ?

Be a man and swallow it.

I was trying to think of a tongue oriented dental pun, but the only thing I could come up with was depressing

Surely now is the time to take it off ?

Don't be a snitch

I like your angle but aren't you going off at a tangent ?

Can't you just share the top level folder, add some permissions, cascade them down without replacing earlier permissions and then give staff a shortcut to the share. If you can't change permissions so easily look at scripting and using CACLS.

what a pity, you don't understand

I think it would split up before long.

We're just expanding into a MAT support situation. I think we'd be looking to expand use of our existing helpdesk software. ManageEngine ServiceDesk Plus. This supports a multi-site configuration, user web portals, email tickets. It's basically a professional quality system, and the basic level is free.

Nah, it'll never wash.

I had this exact issue I think last week. It seems you can't change the UEFI or Legacy boot options if you've done anything else in the BIOS. Exit out the BIOS and power off. Boot up and go into the Bios, into the second screen you posted and click on the greyed out Legacy area, hopefully this will enable you to change things in it. It's my first experience with HP PCs and I'm not hugely impressed TBH.

You could ask Microsoft. Are you just looking to move the domain or all the data as well ? In principle (never tried it) I think you just unfederate the domain and set some passwords. Just checked the RM Support site and they say "Contact us" for instructions on unfederating. Personally I would go down that route.

I think that could be open to abuse.

No it just means we were using it wrong.

Please stop this before Icelander you

Who nose, but I suspect you're barking up the wrong tree.

I see I am going to have to take steps.

That's an elite suggestion