@psx_defector said in IIS Security setup: Best practice isn't up to date. Set it to PCI 1.2, that disables TLS1.0, all the AES stuff, etc. etc. You can also disable them manually in the first screen. Great, thanks.

So using the SYSTEM account appears to work, at least when I manually run the task. So meh w/e. It still requires a user to be logged in, which I might see if I can change that flag as I don't want to rely on my users remaining logged in. But they likely never sign out either.

@travisdh1 said in Server 2012: PS Get-ADGroupMember: @coliver said in Server 2012: PS Get-ADGroupMember: Did you do Import-Module ActiveDirectory ? One of my major pain-points with PowerShell. Why does every module have to be manually loaded. It's not like you have to load them into memory until it's actually needed. No anymore, those are on old OS...

@jaredbusch said in Powershell create shortcut to server root share: @DustinB3403 what about the public desktop instead of hte user desktop? Then it will always be there, regardless of who logs in. Not a huge concern for our use cases as we usually just end up wiping a system and reloading between user changes. I thought about it, but it wasn't critical and as we change things around it becomes a pain to remove the old links to systems that may not exist any more.

This sorted out clipboard | select skip -7| out-string

I believe if PowerShell is your method, you will not be able to do what you are trying to achieve. The only way now is to use the one that has just been advised.

@scottalanmiller said in List All Public Folders in Exchange or Office 365 with PowerShell: Want to get a list of all of the public folders on your Exchange system, whether on premises or hosted, try this: Get-PublicFolder -Identity "\" -Recurse | Get-PublicFolderClientPermission | where{$_.Accessrights -eq "owner"} More on Get-PublicFolder from TechNet That's pretty cool. I was wondering why you were piping into every owner since you could create public folders in Exchange without delegating owners, but then I had remembered you can create them on the client side as well after a root or folders are created in Exchange and added to the client, which is explained in your first pipe. Thanks for the note.

@stess https://blogs.technet.microsoft.com/platformspfe/2014/01/20/integrating-xaml-into-powershell/ look at this. It gives the basics of integrating XAML into a PowerShell script and might be right what you are looking for.

I can't remember where is nabbed it from, but I use the following: Function Mailer { $emailTo = "" $emailFrom = "" $subject="It's broken, damn it" $smtpserver="" $smtp=new-object System.Net.Mail.SmtpClient($smtpServer) $Message = @" Insert a useful/meaningful message here. "@ } Mailer Last line calls the function (duh for you, but a visitor here might not know).

@lakshmana The above helps me and its working but i need the output of that file to be append at the same .csv file which is not working.How to do that ?

@black3dynamite said in Migrating on-premises VHD files to Azure is not rocket science: I can believe Azure still doesn't support vhdx. Although if you use an Generation 2 VM it is the only file supported https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn282285(v=ws.11) Still open case with Azure https://feedback.azure.com/forums/216843-virtual-machines/suggestions/4271962-upload-vhdx

C:\Windows\system32>powershell Set-ItemProperty -Path 'HKCU:\Software\Policies\Microsoft\Windows\Control Panel\Desktop\' -Name ScreenSaveTimeOut -Value 0 Set-ItemProperty : Cannot find path 'HKCU:\Software\Policies\Microsoft\Windows\ Control Panel\Desktop\' because it does not exist. At line:1 char:17 + Set-ItemProperty <<<< -Path 'HKCU:\Software\Policies\Microsoft\Windows\Contr ol Panel\Desktop\' -Name ScreenSaveTimeOut -Value 0 + CategoryInfo : ObjectNotFound: (HKCU:\Software\... Panel\Deskto p\:String) [Set-ItemProperty], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetIt emPropertyCommand

@jaredbusch said in Anyone have a powershell line to create a new admin account: I have a handful of Windows 7 machiens not on a domain. I want to put a new Admin account on them. The current user accounts have admin rights, which I will remove, I have ScreenConnect installed and running with admin perms. So I can pop a powershell via the ScreenConnect command window easily to do this. not tested... maybe this thread can help with PS 2.0. Quoting code here: # Create new local Admin user for script purposes $Computer = [ADSI]"WinNT://$Env:COMPUTERNAME,Computer" $LocalAdmin = $Computer.Create("User", "LocalAdmin") $LocalAdmin.SetPassword("Password01") $LocalAdmin.SetInfo() $LocalAdmin.FullName = "Local Admin by Powershell" $LocalAdmin.SetInfo() $LocalAdmin.UserFlags = 64 + 65536 # ADS_UF_PASSWD_CANT_CHANGE + ADS_UF_DONT_EXPIRE_PASSWD $LocalAdmin.SetInfo()

@manxam Thanks now it works in command prompt from the .bat file

Works great on Fedora 27. dir alias is easier to type btw.

Having TaskScheduler in Windows run PowerShell scritps is like rolling dice depending on the context in which you are running the script... So when in doubt: I always have guaranteed success when starting the PS script from a batch file first from a scheduled task. Create a scheduled tasked using these lines in an elevated powershell window: Creates a scheduled task: $action = New-ScheduledTaskAction -Execute 'C:\ProgramData\scripts\PSKickoff.bat' $trigger = New-ScheduledTaskTrigger -AtStartup $principal = New-ScheduledTaskPrincipal -GroupId "BUILTIN\Administrators" -RunLevel Highest $settings = New-ScheduledTaskSettingsSet $task = New-ScheduledTask -Action $action -Trigger $trigger -Principal $principal -Settings $settings Register-ScheduledTask -TaskName "Scheduled Task Friendly but Meaningful Name" -InputObject $task Note: Change above New-ScheduledTaskTrigger -AtStartup to match your schedule. Here's the info for it. The batch file that the scheduled task runs: Powershell.exe -executionpolicy bypass -File "C:\ProgramData\scripts\yourScript.ps1"

@jaredbusch said in PS: O365 cmdlet issue.: @gjacobse said in PS: O365 cmdlet issue.: For my record later: /wtb codeblock around that... ``` I fixed it.

@scottalanmiller That did the trick. Didn't even cross my mind. Thanks!

Here is a script I made to set up a scheduled task to either launch a PowerShell script, or a batch file. Comment out the $action line that you do NOT want to use. The below script will create a scheduled task that launches a PowerShell script called psScript.ps1. Note that you must execute these lines in an elevated PowerShell window. #Requires -RunAsAdministrator $action = New-ScheduledTaskAction -Execute 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' -Argument "-ExecutionPolicy bypass -NonInteractive -NoLogo -NoProfile -File '\\server\path\to\psScript.ps1'" # $action = New-ScheduledTaskAction -Execute '\\server\path\to\batchFile.bat' $trigger = New-ScheduledTaskTrigger -AtLogon $principal = New-ScheduledTaskPrincipal -GroupId "BUILTIN\Administrators" -RunLevel Highest $settings = New-ScheduledTaskSettingsSet $task = New-ScheduledTask -Action $action -Trigger $trigger -Principal $principal -Settings $settings Register-ScheduledTask -TaskName "kickoff" -InputObject $task If you choose to launch the PowerShell script via a batch file, here's what you need to have in your .bat file: Powershell.exe -executionpolicy bypass -File "\\server\path\to\psScript.ps1"

@tim_g said in PowerShell Regex - How to remove everything after first line?: Actually, I'm sticking to this: $compName = Get-WmiObject win32_ComputerSystem | Select-Object -ExpandProperty Name if ($compName -match "WINDOWS") { $dellTag = Get-WmiObject win32_bios | Select-Object -ExpandProperty SerialNumber Rename-Computer -NewName $dellTag -Force -Restart } Exit Compared to sed, that makes my head hurt. Glad you got it sorted, and an example for when I'll need to do the same thing.

@dafyre said in PowerShell - Script never completes. Is there a session timeout?: @anthonyh said in PowerShell - Script never completes. Is there a session timeout?: @dafyre said in PowerShell - Script never completes. Is there a session timeout?: ROFL. Not a problem. Things working as designed. Next! For what it's worth, my post was intended to be framed from the standpoint of "what am I doing wrong??" rather than "what's wrong with the system?!". I figured I was missing something stupid. Never hurts to have extra eyes. I didn't even think about the potential for this to be a scheduled job... God, I have a case of the Mondays. Not your fault at all. I did not mention it in my OP. Whoops. Perhaps I'm the one with a case of the Mondays.

@dustinb3403 You're welcome ! Glad you got it sorted.

good article thanks and handy script

@gjacobse So basically you want to iterate through a list of computers the same script correct? So do you have a list of computers? What are other steps on your script? because what we can do is the following *$computers = import-csv -Path "c:\script\computers.csv" foreach ($oldname in $computers){ Rename-Computer -NewName $newname -DomainCredential domain\admin -Restart} This assumes you have a CSV file with a oldname and new name columns with computer names.