Configuring MPIO to automatically claim all iSCSI devices

Enable-MSDSMAutomaticClaim -BusType iSCSI

@Dashrender said in Office365 Direct Send without Relay:

@JaredBusch said in Office365 Direct Send without Relay:

For only basic email traffic needs like scan to email, just setup a connector in Office 365.

Exchange Online has various rate limits though. So if you think you will be even close to them, use postfix locally to send out and just add your local WAN IP to your SPF record.

Why wouldn't your local relay still relay everything through Hosted Exchange in O365? or would that be rate limited as well?

Exchange Online has limits. it does not matter from where the email originate. The software was actually setup to authenticate and send email directly with and Exchange Online account during testing.

This quickly hit the rate limits as the client was sending out large amounts of price notifications to users that has signed up for such.

So this site had a local CentOS 7 box setup and Postfix was configured to send mail out. The SPF record was updated and then a connector was also setup to make sure nothing was blocked for no reason.

Inserted a new line of code at line 82 and 87 to read as follows:

icacls \\<server>\d$\Users\$un\* /grant $un:F /inheritance:e /T

This line grants the new employee full access to their network folder and subfolders and items.

Inserted a new line of code at line 82 & 87 to read as follows:

icacls \\<server>\d$\Users\$un\* /grant $un:F /inheritance:e /T

This line grants the new employee full access to their network folder and subfolders and items.

I added a tag for you.

@DustinB3403 Ahh I see, then yes a prompt for input script is best then.

PowerShell Empire has some good modules that will do all that
Check out BloodHound.

@Tim_G Nice catch. Tagged. Thanks!

Planning to test this out soon.

@maalmeida said in I cannot get any invitation from Spiceworks:

@Romo Exactamente. Con el dns no me dejaba entrar y ahora con la ip si pero me muestra eso

Si te muestra eso por que la configuracion por default en servidores del explorer es muy restrictiva, lo cual es normal y recomendable puesto que realmente no se debe navegar desde los servidores.

Lo importante es que con la ip si te intenta cargar el acceso a OWA, si trataras con el puro nombre del servidor tambien te deberia de mostrar lo mismo que con la ip.

If that doesn't work, you might also need to do:
Set-MailboxFolderPermission -Identity "conf-room:\non_ipm_subtree\freebusy data" -User default -AccessRights reviewer

@StrongBad said in Query OneDrive:

Awesome, thank you very much. That's what I was looking for.

yw

@Tim_G said in PowerShell & Office 365 Remoting Broken - Fix:

wusa

Thanks.

Just to clarify: PowerShell is not required here because wusa(.exe) is a regular executable file, not a cmdlet. Any other way that let you execute a program with elevated rights will do (e.g. cmd.exe, shortcuts, ...)

@Mike-Davis said in What should be in Powershell 101 and Group Policy 101 Sessions at MangoCon 2016?:

In the WPA2-Enterprise deployment session, I'll hit on how you push the cert and SSID to your domain joined devices to have the connect automatically to your WPA2-Enterprise SSID.

I like this idea.

@travisdh1 said in Creating an Active Directory Group with PowerShell:

Gah, I'm having bad memories of OpenVMS with the different programs for every single little thing.

It does make for a nice looking and short command-line structure tho.

Oh yeah, SO much different than UNIX.

@momurda said in Add Whitelist Entries in Office 365:

If you run this command again with different addresses/domains, doesnt it overwrite the previous items in the list, unwhitelisting your previous whitelist addresses?

Correct, this is setting the list. You'd have to append the new ones to the command.

@scottalanmiller said in Add Active Directory User to Group using PowerShell:

When we work strictly from Windows Server Core installations we need to be able to do everything from the command line, even user management. Let's add a user that already exists into a group that already exists in Active Directory using only PowerShell.

To do this we have the handy Add-ADGroupMember PowerShell commandlet. This is very easy to use in its basic form, all we need is the name of the group and of the user that we want to add. In this case, I want to add user jane to the group "Domain Admins".

Add-ADGroupMember "Domain Admins" jane

That's it, jane is added automatically. This process, like most, is silent on success. To verify that all is as we want it to be, we can use the Get-ADGroupMember command to look up the members of a group.

Get-ADGroupMember "Domain Admins"

Can also do
Add-ADGroupMember -identity "Domain Admins" -members "jane" -WhatIf
to see if it gets added before actually running the command.

@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@coliver said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

Good article. There is ZERO reason to have a GUI on a Domain Controller. Everything can be done through Server Manager on Windows 10/8

You mean RSAT

Both? You can do a lot of directory management through Server Manager as well.

Ok, agree. Just don't like the Server Manager this much, ugly interface. I want to be sure WHICH drive on WHICH host I'm going to format for example. But that is just my personal opinion and I'm more or less a console fetishist

But when it comes to ADSIedit or AD sites, you really want to have RSAT.

huh?

Those options are generally only there is RSAT is installed.

Sweet. Thanks for getting this for us @adam-ierymenko

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

I learned something new today. I have been using the shutdown command for years. I never realized you could rename a PC with it.

shutdown doesn't do the renaming, you just have to reboot after you rename.

I use "m" instead of c for computer name

/c is the comment for the logs to tell them that you just "Renamed Machine", it doesn't rename it, it literally puts "Renamed Machine" into the reboot logs.

Ok. Got ya.

It does work really well, especially for form building. It's a trial thing, so it'll expire after a period of time. Porbably worth it if you're doing a lot of PowerShell work, tho'.