halbaradkenafin

They are still going, one of their leadership (Mangala) also runs a weekly roam into null with a theme. They basically fly around with ~100 people+ in fleet and shoot whatever they run into. It's been good fun when I used to go on them. A quick skim through my losses and it looks like I only ever lost about 400mil worth of stuff, never lost of my T3s thankfully but I never risked them in PVP as the skill loss wasn't worth it (the isk wasn't too big a deal since they weren't super pimped and only about 1.5 - 2 bil value).

And the inevitable lemmings who'd jump/warp before told and die horribly.

That's about an hour of missions (level 4) or a few wormhole sites (if you get lucky drops) or about half an hour of Incursions (if they are still a thing).

I used to play a few years ago and still have most of my stuff. People in my gaming group still play weekly, I think they've been doing some pretty cool things with the Heresy armies they've been building up. A small group of us are considering starting up Mordheim again though for a bit of change, probably just a small campaign over a few months.

I'm in the "used to play too much" group as well, spent some of last year doing stuff with random corps and alliances and then got bored of the stuff happening and gave all my isk away to Eve Uni, kept a few ships and stuff for the memories (including a large rigged Drake I got from a friend) and then never logged in again. I get the urge to play again sometimes but remember I have no isk and really don't want to grind it again and that's enough to keep me away and playing other things instead.

We've got two policies in place, one for staff who want to use our RDS system and one for everyone else. The general policy is: *At least 6 characters *At least one upper case, one lower case and one number *Lockout after 3 failed attempts *Currently no expiry but we may change that in the next few months to 60 days or something *Can't contain the users name Our Remote Access policy is a lot more convoluted and has things like not being able to use 3 consecutive characters in different passwords. We've also got an alternate method which uses pass phrases, which require at least 15 characters, at least 2 spaces and at least one upper case letter. Most staff choose the pass phrase option as it's less complicated than all the complex rules we've got in place for the password option.

Last place I got a cheque from the school and a small box of biscuits from a few of the science staff since I'd visit sometimes to share biscuits with them.

A few things to check: All links are relative rather than static, if it's being developed in something like Dreamweaver the sometimes it decides to just magically put in a static link rather than relative. Browse to the site using it's internal server name rather than IP, could be hitting smoothwall and being blocked for some reason nslookup for the IP should hopefully show the internal name for the server Without getting a look at the code/site it's just some guesses.

From the few episodes I watched a while ago (and will get back to) he's one of those actors who does reasonably well in films but can take a role to a new level when given the extra time that a series provides. I'd really like to see more film actors make that step to series acting (assuming the role/series is fitting for them anyway).

Saw this on Reddit yesterday and added it to my $Profile straight away, going to have some fun with it.

Alternatively if you've got Impero just hit the button in there that disables sound for the student group.

You could use GPP to set the Windows Audio service to disabled. That's the quickest way I can think of, plus it's easy to reverse by just changing the setting to Automatic again.

I'll take a caffeine-free irish coffee please.

Does it have any logging already included? If not it's worth either adding some manually using Write-Output or temporarily redirecting the error output to a text file with date/time stamps in case it's an issue with the powershell script itself. If there is no output from that then I'd guess it's an issue with the task schedule itself, I'd check the History and see if anything at all is logged there, there might also be some way to enable more verbose logging through event viewer or something.

What does the scheduled task do? Is it a script or something? Is there any logging you can enable as part of it, either to Event Viewer or to a text file.

Delete or rename the local GroupPolicy folder which is in C:\Windows\System32 and is usually hidden. Rerun gpupdate /force after renaming/deleting the folder and it should force a full refresh of the policies.

Pretty much just doing whatever comes up, read some powershell blogs and maybe even finish the script to automate the prestaging of new PCs into SCCM and AD. If I get really bored I might refactor a bunch of the scripts I've got to streamline them a little and consolidate some of the more useful functionality into a central repository.

Has User B logged in to that PC since the policy update? I've found it can sometimes not update the policy for users even if they are in the same OU as another user who has logged in.

I've got a powershell script to handle this, just need to change the root directory to whatever it will be and add the domain short name to the $Permissions variable. I'd also remove Domain Users from the parent folder permissions before running this. $Folders = Get-childItem -Path "" $InheritanceFlag = [system.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [system.Security.AccessControl.InheritanceFlags]::ObjectInherit $PropagationFlag = [system.Security.AccessControl.PropagationFlags]::None $objType = [system.Security.AccessControl.AccessControlType]::Allow foreach ($TempFolder in $Folders) { Write-Output -InputObject "Loop Iteration" $Folder = $TempFolder.FullName $UserFolder = $TempFolder $acl = Get-Acl -Path $Folder $permission = "\$UserFolder","Modify", $InheritanceFlag, $PropagationFlag, $objType $accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission $acl.SetAccessRule($accessRule) Set-Acl -Path $Folder -AclObject $acl } As for how they did it I suspect it's caused by Domain Users having full control and them possibly being able to see the root path in My Computer (either next to the drive icon or once navigating their drive). I'm not 100% on that though so it might not be exactly how they did it.

Mario Party 10 will result in some good laughs if the others are anything to go by.

No problem, we had a similar issue here and I had the majority of the script ready to go anyway.

Modify should allow that and the permissions should force inheritance down each level, if not then I'll have a look into it. Edit: Looks like the string you want is "DeleteSubdirectoriesAndFiles", just swap it with modify and it should add the permissions together I think. If not then you'll probably have to use "DeleteSubdirectoriesAndFiles, Modify" but I haven't tested that so it may be wrong.

An IF statement afterwards would be the best way. Something like: if ($WantCompression -notmatch "^[nyNY]+$") { $WantCompression = "Y" } That would mean that if they don't enter a Y or N (upper of lower case) then it defaults to Y (or N if you'd prefer)

Yes or you can paste it into notepad, change the few things needed and then copy/paste it into a Powershell window and it should work.

$Folders = Get-childItem -Path "" $InheritanceFlag = [system.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [system.Security.AccessControl.InheritanceFlags]::ObjectInherit $PropagationFlag = [system.Security.AccessControl.PropagationFlags]::None $objType = [system.Security.AccessControl.AccessControlType]::Allow foreach ($TempFolder in $Folders) { Write-Output -InputObject "Loop Iteration" $Folder = $TempFolder.FullName $acl = Get-Acl -Path $Folder Write-Output -InputObject "$TempFolder" $permission = "\Drive_PupilProfilesDrive","Modify", $InheritanceFlag, $PropagationFlag, $objType $accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission $acl.SetAccessRule($accessRule) if (Test-Path "$Folder\Desktop") { Set-Acl -Path "$Folder\Desktop" -AclObject $acl} if (Test-Path "$Folder\Documents") { Set-Acl -Path "$Folder\Documents" -AclObject $acl} if (Test-Path "$Folder\Music") {Set-Acl -Path "$Folder\Music" -AclObject $acl} if (Test-Path "$Folder\Pictures") {Set-Acl -Path "$Folder\Pictures" -AclObject $acl} if (Test-Path "$Folder\Videos") {Set-Acl -Path "$Folder\Videos" -AclObject $acl} } Should do it, you'll need to set the path to the root folder at the top and set the domain short name and group name in the $Permission variable. If you get any errors then paste then here and I'll have a look, shouldn't run into any problems as it checks if a folder exists before trying to set the permissions.