Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 301
Reply with quote  #1 
 When I want to "install-module -name MSonline" I get this error :
minasi.jpg 
Is it safe to use the "-AllowClobber" parameter as suggested by the error message ?
On this server the Azure AD Connect service is installed.
And I already installed the Powershell AzuredAD module as well.

Pieter


__________________
Pieter Demeulemeester
0
jsclmedave

Administrator
Registered:
Posts: 506
Reply with quote  #2 
Quote:
Originally Posted by Pieter
 When I want to "install-module -name MSonline" I get this error :
minasi.jpg 
Is it safe to use the "-AllowClobber" parameter as suggested by the error message ?
On this server the Azure AD Connect service is installed.
And I already installed the Powershell AzuredAD module as well.

Pieter


Thought MSONLINE has been depricated..?



__________________
Tim Bolton @jsclmedave
Email: [string](0..20|%{[char][int](32+('527377347976847978324785847679797514357977').substring(($_*2),2))}) -replace ' '  

New to the forum? Please Read this
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 301
Reply with quote  #3 
>>Thought MSONLINE has been depricated..?

That's why I didn't installed MSonline in the first place.
But I had a training yesterday and the trainer advised us to install both modules.



__________________
Pieter Demeulemeester
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 940
Reply with quote  #4 
WINS is being depricated for how long?

You can use clobber, but only install module you need, not because you were told to do it.
Most things you need to do, you should be ok to do on your own machine against Azure/ M365 or whatever they call it.

You possible have a module conflict, or dependancy issue, .Net comes to mind all the time.

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
cj_berlin

Avatar / Picture

Senior Member
Registered:
Posts: 431
Reply with quote  #5 
OK, late to the party, but here's this.

First, you are fine to -Allow Clobber at *install* time. And even if there are overlapping cmdlets, you can

  • Use a prefix at import time to distinguish them
  • Use fully qualified cmdlet names in your scripts
wich is both kind of shitty but if you have to manage vSphere and Windows Failover Clusters from the same PowerShell session, you basically have to choose the lesser evil there.

Rob Holt from the PowerShell Team did a phantastic talk on the module system at this years' PSConfEU: 

 

__________________
Evgenij Smirnov

MVP Cloud & Datacenter Management
My personal blog (German): http://www.it-pro-berlin.de/
My stuff on PSGallery: https://www.powershellgallery.com/profiles/it-pro-berlin.de/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 301
Reply with quote  #6 
Okay, I thought simple question, simple answer...
Since both modules come from Microsoft, I guess I'll take the risk and install both of them.


__________________
Pieter Demeulemeester
0
Infradeploy

Avatar / Picture

Senior Member
Registered:
Posts: 186
Reply with quote  #7 
And if they do collide import the module you want before you issue the first command. Like with Azuread and Azureadpreview modules.
__________________
Have SpaceSuit, Will Travel

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.