User Profile
diecknet
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: Am I doing something wrong?
Preston_Cole Do your CSV files really look like that? I mean just one column for each file? If they do, then the problem is, that in your loop you specify properties (=column names) that don't exist in your CSV files. For example $project.ProjectName would refer to the value of the row "ProjectName" in your CSV of the current object.Re: Script to get AD group and members details but group name is to long
cvaxelWhat's the actual problem? Is the generated string too long for an Excel Sheet? You can check the length like this: $group.Length And if it's longer than 31 character you could shorten it like this: $group.Substring(0,31)Re: Get-ChildItem and Get-WmiObject cim_datafile showing different results
If your chosen cmdlet doesn't support executing against a remote system, you can try PowerShell Remoting. Essentially: Invoke-Command -ComputerName $YOUR_REMOTE_SERVER -Command {YOUR COMMAND} More infos in the docs: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote?view=powershell-5.1Re: WARNING: The provided service principal secret will be included in the 'AzureRmContext.json' file
DK wrote: I added everyone with full control permissions to .\Azure. That is pretty much the opposite of the meaning of the Warning: DK wrote: WARNING: The provided service principal secret will be included in the 'AzureRmContext.json' file found in the user profile ( C:\Users\username01\.Azure ). Please ensure that this directory has appropriate protections. You are apparently connecting to Azure with Connect-AzAccount using a Service Principal. The Secret (which equals to a password) is getting saved as plaintext in the user's profile. If you add Everyone with Full Control permissions to that folder, you are not protecting it. Just make sure that no other users can access that folder. The default user profile permissions should be sufficient for that. You can disable the saving of credentials for this PowerShell session using Disable-AzContextAutosave -Scope Process or just Disable-AzContextAutosave to disable it for the current user.Re: Solution - if you can't connect to WVD desktop and got a message about Gateway error
serge it should also work with Cloud-Only (Azure AD plus Azure AD Domain Services) users. But the user has to change their password themselves in Azure AD/Office 365 first. If you go with the initial password there is no legacy password hash transferred from Azure AD to Azure AD Domain Services.Monitoring Azure RecoveryServices (Windows Server Backups to Azure using MARS)
Hello, I'm using the MARS agent to backup on-premise Windows servers to Azure Recovery Services. Now I'm trying to check for backup statuses, using PowerShell 5.1 and the Az 2.5.0 PowerShell Module. # authentication is handled before $vault = Get-AzRecoveryServicesVault -Name "BackupVault1" $Containers = Get-AzRecoveryServicesBackupContainer -ContainerType Windows -BackupManagementType MARS -VaultId $vault.ID foreach($Container in $Containers) { Get-AzRecoveryServicesBackupItem -VaultId $vault.ID -Container $Container -WorkloadType WindowsServer } Apparently the WorkLoadType "WindowsServer" does not exists, but all the others that should be valid (AzureVM, AzureSQLDatabase, AzureFiles, MSSQL) are not working either. I got that WorkLoadType from the PowerShell module, eventhough it doesn't exist in the documentation. Any ideas?Re: Teams-SfB Forced Migration Pains
PeHobe I don't see any way of going back to Skype. I just tried setting the tenant upgrade policy and user upgrade policy to "islands" or "sfbonly" via PowerShell, but it's not possible anymore. I had the slight hope that it would be still possible there, but nope. > Grant-CsTeamsUpgradePolicy -Global -PolicyName tag:islands TeamsUpgradePolicy cannot be set because Microsoft has already upgraded this organization.It's not possible to create a new plan for an EXISTING GROUP, if "Group creation" is disabled
Hello, apparently it's not possible to create a new plan for an existing group, if the creation of groups is disabled in Azure AD. I disabled the creation of groups for normal users (https://docs.microsoft.com/en-us/office365/admin/create-groups/manage-creation-of-groups?view=o365-worldwide). Only administrative groups are allowed to create Office 365 groups in the tenant now. Teams (and so Office 365) are created by the IT department. End users can't add new Plans to their Teams, even if they are the Owner of the team. In my opinion this is unexpected behavior. Is this really intended? EDIT: Apparently it's possible to add new plans to existing groups, that already have atleast one plan added. I guess there are some processes in the background, that add attributes/infos to the Office 365 Group mailbox and Sharepoint team site when adding the first plan to a group.
