No 

Yes

Reg key in a handy commandlet to disable the new menu and use classic;

reg.exe add “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32” /f /ve

Then just restart explorer.exe

To bring it back run;

reg.exe delete “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}” /f

 

GD Star Rating
loading...
GD Star Rating
loading...

Recently added group members to a 365 Group with a Shared Mailbox however the group could not be added to the persons Outlook

In the end we had to use Webmail to access the Mailbox , group Links can be found in Azure AD for the Groups

GD Star Rating
loading...
GD Star Rating
loading...

 “Form Templates, Site Assets and Style Library are default document libraries containing the design, meta data and resource of the site and need not be migrated, unless required. Documents document library is the focus and should be migrated.”

1. Logon to SharePoint Admin Center

2. Go to Active Sites and click on Export.

3. In the CSV file generated, filter by Column C Teams . You may have Communications site or SharePoint Classic site or Team site as your template type. But do ensure when you see Team site, Column C for Teams is false. If column C is true and it is a Team site then do follow the below note.

Note: Team site is part of our Teams Migration solution offering and you may enquire on the

Teams Collaboration license with our sales team.

4. Under Column B, URL, you will see a list of sites URLs you have. Go to each of these sites to find out the name of the document library as well as the URL.

5. On the site URL, click on the Gear Icon and select Site Contents.

6. In Site content and under type, you will be able to identify the Document Libraries.

Form Templates, Site Assets and Style Library are default document libraries containing the design, meta data and resource of the site and need not be migrated, unless required.

Documents document library is the focus and should be migrated.

7. In the above example, the site URL is https://m365x165379.sharepoint.com/sites/benefits/Shared%20Documents/

Hence m365x165379.sharepoint.com is the Endpoint URL to be set in MigrationWiz. And in the SharePoint project’s line item, the document Library path is “sites/benefits/Shared%20Documents”.

Alternatively you can select to Autodiscover function in MigrationWiz. But do ensure to remove away those Teams enable Teams site.

8. This example is considered as 1 count of the shared document license required.

9. Do the same across the other URLs identified in step 4, to identify the document libraries.

And note the URL and document library path as per step 7.

GD Star Rating
loading...
GD Star Rating
loading...

https://community.teamviewer.com/English/kb/articles/5265-commercial-use-suspected

 

We have successfully reset the TeamViewer ID(s) you submitted via the form provided earlier.

We acknowledge that you are using TeamViewer for private use only on these devices.


Troubleshooting:

I have been reset but I’m still getting the message saying I’m using TeamViewer commercially. What can I do?

If you are still getting the pop-up saying you are using TeamViewer commercially, it is most probably due to the fact that:

  1. the TeamViewer ID of the remote device you are trying to connect to might be flagged as being commercially used.
    Please keep in mind that a TeamViewer connection always involves two devices (TeamViewer IDs) and that we are presenting the pOpUp on both sides of the connection.
    If you think that this is not the case and that connecting to this device is private use, please repeat the process and fill out an additional form for this/these TeamViewer ID(s): https://www.teamviewer.com/en/reset/

  2. the TeamViewer ID(s) that you submitted is/are invalid or do(es) not exist.
    In order to prevent this, please check if the data you have submitted is correct. To do so, please open your signed declaration (PDF-file) and check if the TeamViewer ID(s) you provided match(es) the TeamViewer ID(s) you are using.
    In this case, please repeat the process and fill out a new form for this/these TeamViewer ID(s): https://www.teamviewer.com/en/reset/

Please note that if your usage pattern changes and your TeamViewer connections are deemed to be commercially flagged, your reset may be reverted at any time.

GD Star Rating
loading...
GD Star Rating
loading...

Originally I tried to use the New-MailboxRestoreRequest powershell cmdlets but it was bugging out on me… not surprising since the both inactive and new mailboxes shared many of the same details. Turns out I needed to use the ExchangeGUID (Step 10)

 

I could check restore status using the following lines:

$requests = Get-MailboxRestoreRequest | select targetmailbox, RequestGuid

ForEach($request in $requests){Get-MailboxRestoreRequestStatistics -Identity $Request.RequestGuid}

 

Re-provisioning mailboxes that didn’t want to exist ‘couldn’t be found’

Additionally Admin Console would say something like “This user’s on-premises mailbox hasn’t been migrated to ?Exchange Online?. The ?Exchange Online? mailbox will be available after the migration is completed”

To fix this; I needed to clear the msExchMailboxGUID attribute and set msExchRemoteRecipientType to 1. Turns out mailboxes that were migrated from on-prem will carry a flag and GUID for their historical on-prem junk which can prevent a mailbox from provisioning in EXO. Normally not a problem but in this case it was!

GD Star Rating
loading...
GD Star Rating
loading...

I have a customer with a Nimble CS210 running 5.x, that is wanting to do a group merge to migrate the data to a new Alletra 6010 running 6.x OS.

CS210 (AF-129379) is currently running with NimbleOS 5.0.10 and it can only go up to 5.3.0.6010 (AF-300423) is now on AlletraOS 6.0.0.400 and it cannot go down to 5.x.

As such, group merge is not possible.Therefore there are only 2 ways for data migration:1) Replicate all volumes from CS210 to 6010, plan a downtime, shutdown all hosts, perform a final snapshot and replicate. Remount volumes from 6010 on hosts.2) Host-based migration.

GD Star Rating
loading...
GD Star Rating
loading...
Customer has 2012 DC’s with NPS and the Azure MFA extension for their Cisco Meraki Client VPN
 
All staff were not able to connect to the VPN from 8am. I have not found why it started at this time. Users before this were able to log in…
 
Event Viewer showed Unknown username or bad password in use.
 

 
The NPS MFA extension leads you down a path that isn’t correct (for me). Dont trust this.
 

 
Also dont trust the reason codes in the NPS logs
You may see reason code 21, <Reason-Code data_type=”0″>21</Reason-Code></Event> Further pointing to MFA extension issues.
 
 
 
Run with powershell and select option 1 to temporarily remove the MFA requirement and attempt a login to prove its not MFA.
 
New errors in NPS logs.
I was getting <Reason-Code data_type=”0″>16</Reason-Code> Not the most helpful and there are LOTS of results. But I found the below recent article which fixed it for me. 
 
I did apply these keys for all the domain controllers. But that might be overkill and unnecessary. The real fix is to get off server 2012.
 
 
 
This isn’t complete yet, after enabling MFA I now have TLS and cipher errors from the MFA plugin. 
 
But hopefully this will be an easy fix.
 

GD Star Rating
loading...
GD Star Rating
loading...

https://infosight.hpe.com/welcomecenter/software-config/arraySetup?model=6010&product=alletra

https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_Installation_Guide_for_HPE_Alletra_6000_WC.pdf

Shortlist

  1. Use the TAB pullout on the HPE Alletra 6000 to record both the Nimble and the HPE Serial Numbers from the device
  2. Patch Eth0A in on both controllers ( this will be used for management )  and power on the Unit ( Sometimes takes 10 minutes for it to start you can plug in a screen to confirm it goes to login ) 
  3. Download and install Install HPE Storage Toolkit on the Windows Host  – https://infosight.hpe.com/InfoSight/media/software/active/public/1/293/Setup-NimbleNWT-x64.7.0.0.31.zip
  4. Run this on a PC on the same Subnet and VLAN as the Unit. The Unit by default does NOT grab a DHCP address , it grabs an address on the 169.x.x.x , the Storage Toolkit finds this via broadcast. The software then opens a Webpage so you can administer this
  5. Go through setting up IP \ NTP etc on the unit , after the last page it will give you a “Use subscription key to activate device” and it will fail to join to Greenlake
  6. Login with your existing customer HPE Passport account and create a New Greenlake account for the Company  ( see Creating an HPE GreenLake company account ) 
  7. After this is done install the Data Services Cloud App See (Adding the Data Services Cloud Console app to an HPE GreenLake company account )
  8. Create an Administrator role for your new user in Data Services Cloud Console ( Adding assignments and scopes to the Data Services Cloud Console app ) 
  9. Add Storage Device to Greenlake ( Adding storage systems to the Data Services Cloud Console app ) using Use subscription key to activate device
  10. Assign the Storage Device to the Data Services Cloud Console ( Adding assignments and scopes to the Data Services Cloud Console app ) 
  11. After this to go  Data Services Cloud Console and Welcome page, click Launch in the Setup Service tile. This is where you will configure the device with Data IPs and other settings
  12. After this is complete , you will then be able to access the Nimble OS Dashboard on the Device locally

 

 

Activating software entitlements

When an HPE Alletra 6000 storage system is ordered, HPE automatically emails an Electronic Software Delivery Receipt. The email contains a link that enables you to activate entitlements for the products in the order. For example, an order might include HPE Data Ops Manager Reserved SaaS 1-year Subscription.

Prerequisites

Locate the HPE Electronic Software Delivery Receipt email that was received for the order.

Procedure

1.      Open the Electronic Software Delivery Receipt email and click Access Your Products.

2.      Log into My HPE Software Center with your HPE Passport account credentials. The Activate page opens.

(If you do not have an account, click Create Account to create one, then continue.)

3.      On the Activate page, under Step 1: Select Products to Activate, select the products and click Next.

4.      Under Step 2: Designate Activatee, select whether you are activating the products for yourself or another user, and then click Activate. The product activation begins. When activation is complete, HPE sends an Activation Receipt email.

 

 

Creating HPE GreenLake user accounts

HPE GreenLake is a cloud portal that provides everything-as-a-service solutions for HPE customers and partners. To enable management of your HPE Alletra 9000 storage system, you must have an HPE GreenLake Cloud Services user account.

If you already have an account, you can skip this step and go to Creating an HPE GreenLake company account.

 

Procedure

1.      Open your HPE Cloud invitation email. Click the link to the Sign In to HPE page. If you have an HPE Support account or HPE InfoSight account, you can use those credentials to sign in.

2.      Click HPE Set Up Account. Enter your first and last name, email address, country, and accept the terms of use. Click Sign Up.

3.      Monitor your email for a verification email. Click Verify Email to verify your identity.

4.      Create and confirm the password to use for the account. Then click Finish.

 

Creating an HPE GreenLake company account

IMPORTANT: By creating an HPE GreenLake company account, you become the super administrator for the account.

If you are adding a storage system to an existing company account, you can skip this step and go to Adding the Data Services Cloud Console app to an HPE GreenLake company account.

Prerequisites

You must have an HPE user account. If you have an HPE Support account, HPE Passport account, or HPE InfoSight account, you can use those credentials to sign in.

Procedure

1.      If you are not already signed into HPE GreenLake, enter your email address and password to sign in. You can sign in at https://common.cloud.hpe.com.

2.      Under Create a New HPE GreenLake Company Account, click Create Account.

3.      Enter the following:

o    Company name

o    Country

o    Company address

o    Zip/Postal code

o    Phone number

4.      Review and accept the legal terms, then click Create Account. Your company dashboard opens.

5.      Optional. To invite other users to join the company account, you click Send an Invite.

 

Adding the Data Services Cloud Console app to an HPE GreenLake company account

The Data Services Cloud Console is an application in HPE GreenLake for managing all your storage devices. To use the Data Services Cloud Console app, you must add it to an HPE GreenLake company account.

If you already have added the app to the account, you can skip this step and go to Adding assignments and scopes to the Data Services Cloud Console app.

Prerequisites

·         You must have a HPE user account. If you have an HPE Support account or HPE InfoSight account, you can use those credentials to sign in.

·         You must have permissions for managing the company account.

Procedure

1.      If you are not already signed into HPE GreenLake, enter your email address and password to sign in.

2.      If your user account is associated with more than one company account, select the company account to add the Data Services Cloud Console app. The company account dashboard page opens.

3.      Click the App Catalog tile. The App Catalog page opens.

4.      In the Choose Region menu at the upper right, select the geographical region that is closest to you. For example, the US West, EU Central, or AP East. The available apps for the region are listed.

5.      In the list of apps, locate the Data Services Cloud Console app and click Add, then accept the HPE Application Terms. The app is added to the company account.

6.      After the app is added, its Launch button is displayed.

IMPORTANT: Before launching the Data Services Cloud Console, you must add permissions to access the app. See Adding assignments and scopes to the Data Services Cloud Console app.

 

Adding assignments and scopes to the Data Services Cloud Console app

Add the permissions necessary to access the Data Services Cloud Console. If you have already added assignments and scopes to the instance of the Data Services Cloud Console app, you can skip this step and go to Adding storage systems to the Data Services Cloud Console app.

Prerequisites

You must have an HPE user account. If you have an HPE Support account or HPE InfoSight account, you can use those credentials to sign in.

Procedure

1.      On your company dashboard, in the Assign User Access box, click Assign Roles.

2.      On the Assignment page, click Create Assignment.

3.      On the Create Assignment page, search for the user, and then click Add.

4.      In the Add Roles dialog box, select Data Services Cloud Console, select Administrator, and then click Add.

5.      On the Create Assignment page, click Add Scope (next to the Data Services Cloud Console application).

6.      In the Cloud Services Cloud Console Scopes dialog box, select each applicable region and then the App. Next, select the available scopes and then click Add.

7.      On the Create Assignment page, click Create Assignment.

8.      Verify that the role and scope types are correct.

 

Adding storage systems to the Data Services Cloud Console app

To manage an HPE Alletra 6000 storage system, you must add it to an instance of the Data Services Cloud Console app.

Prerequisites

·         You must have an existing HPE user account. If you have an HPE Support account or HPE InfoSight account, you can use those credentials to sign in.

·         You know the HPE Alletra 6000 storage system Serial Number and Subscription Key. These can be found on the Activation Receipt email.

Procedure

1.      From the HPE Data Services Cloud Console menu (upper left), select Manage.

2.      Click Device Management, then Add Devices.

3.      Select Storage Devices for the Device Type, then click Continue.

4.      Enter the Serial Number and Subscription Key for the storage system, then click Enter. Repeat this step for each additional storage system (if any), then click Add Devices.

5.      Select the storage systems to add and then click Add Assignment.

6.      Under Storage Devices, select Data Services Cloud Console for the application, and select the application instance (region) to assign the devices. Then click Next and Finish.

7.      Select Device Management and verify that the new storage systems are listed.

GD Star Rating
loading...
GD Star Rating
loading...