Search found 4 matches
- Mon Jul 23, 2018 4:51 pm
- Forum: Office365 for LabTech
- Topic: 2.0.0.74 - Issues with powershell scripts
- Replies: 8
- Views: 20667
Re: 2.0.0.74 - Issues with powershell scripts
Gave the updated version a try this morning. It looks like there's an encoding error and missing double quote in the MSOLUSERS powershell script that is causing the line to break. $strUserPrincipalName = if ($objUser.UserPrincipalName){if($objUser.UserPrincipalName -contains '"){$objUser.UserPr...
- Thu Jul 12, 2018 5:56 pm
- Forum: Office365 for LabTech
- Topic: 2.0.0.74 - Issues with powershell scripts
- Replies: 8
- Views: 20667
Re: 2.0.0.74 - Issues with powershell scripts
This will fix your MSOLUSERS script. The character being returned is ’ and not ' which is why it is not being escaped. $strFirstName = if ($objUser.FirstName){if($objUser.FirstName -contains '"){$objUser.FirstName.Replace("'","''")}else{$objUser.FirstName.Replace("’&quo...
- Wed Jul 11, 2018 5:01 pm
- Forum: Office365 for LabTech
- Topic: 2.0.0.74 - Issues with powershell scripts
- Replies: 8
- Views: 20667
Re: 2.0.0.74 - Issues with powershell scripts
The trickier Powershell bug I found is with escaping single quotes. I had one client that was not populating any informtion at all, but when I manually ran the powershell script in ISE, it came back with good results. Once I ran the plugin in Debug mode, I figured out what the problem was. In Powers...
- Wed Jul 11, 2018 4:59 pm
- Forum: Office365 for LabTech
- Topic: 2.0.0.74 - Issues with powershell scripts
- Replies: 8
- Views: 20667
2.0.0.74 - Issues with powershell scripts
Hey, great plugin! I found a couple of bugs in the Powershell on the current build, one is a really simple one, the other seems a little more involved. I also ran into a weird GUI glitch where it kept data incorrectly when switching between clients. No Sharepoint data is being collected due to a bug...