Good afternoon,
I've successfully installed the plugin, configured it, added a client and initiated a scan. The client has Office 365 Plan 1 mailboxes only; no Azure and no Sharepoint.
I get the Groups but none of the mailboxes appear in the Exchange tab. I have enabled debugging and there are no errors. I checked the plugin_sw_office365forlabtech_mailboxes table and can see all of the mailboxes there.
What could the problem be?
Thanks.
No Mailboxes appear
Re: No Mailboxes appear
Interesting,
What does this query present to you when run?
What does this query present to you when run?
SELECT UserPrincipalName as UserID, DisplayName as UserName FROM plugin_sw_office365forlabtech_users Where ClientID = ""
Re: No Mailboxes appear
Good morning,
No results are returned.
Let me know how to proceed.
Thanks.
No results are returned.
Let me know how to proceed.
Thanks.
Re: No Mailboxes appear
I am assuming you placed a "client ID" in the quoted area of command?
Lets try this? if any data is in the user list this will reveal it.
Lets try this? if any data is in the user list this will reveal it.
If nothing then please run a AZURE scan in debug mode from plugin console and post that as a block quote here. Let me inspect it to see what might be the issues.SELECT UserPrincipalName as UserID, DisplayName as UserName FROM plugin_sw_office365forlabtech_users
Re: No Mailboxes appear
Good morning,
That table is empty.
I rescanned including Azure (though the one client configured for this plugin does not use Azure AD), and the result provided this error.
Starting data collection from Office365
Checking MSOnline Modules are in the 64bit PoSh folder
2281 - 1.0.9031.1
Validating script folder is available
Test for MSOLUSERS functions on probe
Found current MSOLUSERS
Executing MSOL User Scans on [1] Clients
Processing [ClientName] -> Client Failed Update
2281 - bad data or errors returned - Processing -File '-Office365Username' failed because the file does not have a '.ps1' extension. Specify a valid Windows PowerShell script file name, and then try again
I found the folder that I think these scripts are run from in C:\Windows\Temp\Office365. The contents are shown in the screenshot attached. Is there something missing?
Thanks.
That table is empty.
I rescanned including Azure (though the one client configured for this plugin does not use Azure AD), and the result provided this error.
Starting data collection from Office365
Checking MSOnline Modules are in the 64bit PoSh folder
2281 - 1.0.9031.1
Validating script folder is available
Test for MSOLUSERS functions on probe
Found current MSOLUSERS
Executing MSOL User Scans on [1] Clients
Processing [ClientName] -> Client Failed Update
2281 - bad data or errors returned - Processing -File '-Office365Username' failed because the file does not have a '.ps1' extension. Specify a valid Windows PowerShell script file name, and then try again
I found the folder that I think these scripts are run from in C:\Windows\Temp\Office365. The contents are shown in the screenshot attached. Is there something missing?
Thanks.
- Attachments
-
- Capture.PNG (15.32 KiB) Viewed 17531 times
Re: No Mailboxes appear
Can you post a picture of the configs window?
Re: No Mailboxes appear
Aha! I think that the issue was that Azure needed to be selected even though we don't use Azure-AD for this client.
I now have a list of users!
Thanks so much.
Is there any chance that the Open Shell button can be limited by Automate user role? I'd really like to prevent our Level-1 techs from having access to this.
Thanks again.
I now have a list of users!
Thanks so much.
Is there any chance that the Open Shell button can be limited by Automate user role? I'd really like to prevent our Level-1 techs from having access to this.
Thanks again.
Re: No Mailboxes appear
Awesome, glad to hear that. That is exactly where I was going with the request for config. AZUER is needed on all scans as it sets the company profile up and user lists.
As for added permissions there is no way currently to limit user access.
As for added permissions there is no way currently to limit user access.