| T O P I C R E V I E W |
| JSCLMEDAVE |
Posted - 03/05/2010 : 11:34:05 AM
"Servermanagercmd.exe is deprecated, and is not guaranteed to be supported in future releases of Windows. We recommend that you use the Windows PowerShell cmdlets that are available for Server Manager."
Hopefully "you" (was not me) have not wasted about two months learning this...
Just in case you missed these -
"Servermanagercmd is deprecated, and is not guaranteed to be supported in future releases of Windows. Ah, Servermanagercmd, we hardly knew ye ..."
Installing, Managing and Troubleshooting Windows Server 2008 R2
http://www.minasi.com/08r2class/
Control Windows Features with DISM - The new feature-management tool Servermanagercmd.exe in Windows 7 and Windows Server 2008 has its pros and cons
http://www.windowsitpro.com/article/utilities/control-windows-features-with-dism.aspx
7/12/2009
Windows Server 2008 R2 Server Manager
http://joeelway.spaces.live.com/blog/cns!2095EAC3772C41DB!2606.entry
Servermanagercmd
Updated: August 12, 2009
http://technet.microsoft.com/en-us/library/ee344834(WS.10).aspx
|
| 12 L A T E S T R E P L I E S (Newest First) |
| wobble_wobble |
Posted - 03/07/2010 : 4:59:03 PM
David,
I honestly can't answer that. I've read that its needed, but you read a lot of stuff. In single subnet's your probably OK, but I've always made sure WIN's has transfer over and is operating. Some of the other lads would be more knowledgeable on more complex Exchange installs and may chirp in.
The error code it throws up is just that an error message. With MS attitude towards better installers its to be expected, what with them offering to check for pre-requisites, having the web links or maybe even software in the installer is cool. There was an error message in the Exchange 2003 installer telling you that Exchange 2003 was not compatible with Server 2003, you could ignore the error message. Never did find out what it all meant.
With regard to the Powershell independent group engineering, yup, lads get a bloody life. How hard is it to have one set of rules for developing/ using a supposedly standardised management language and sticking to it?
Edit
Mark, I think both yourself and Don mentioned about Servermanagercmd and more back in the 2008 conference, that almost 2 years ago. Dosen't time fly. |
| aval |
Posted - 03/07/2010 : 2:51:40 PM
quote:
And can multiple Exchange Servers exist without WINS?
Pending purchase of a second SAS drive, I want to virtualize two with ESXi (objective: practice LCR, SCR and maybe CCR).
So... do I need to configure.... WINS???!!!!
(Never used it in 10 years - when we still had 95/98 I just let broadcast do the job - right, single subnet).
And please don't tell me it's still around in W2K8 R2!
MS can't seem to drive a stake in its heart (like Dracula). |
| Jazzy |
Posted - 03/06/2010 : 6:20:17 PM
O no, that's not the problem. It annoys me that all product groups choose their way to own way to implement PowerShell. I mean, common engineering criteria are great but the way they're doing it now is very bad for general acceptance of PowerShell. There's no consistency.
Some examples. To start using the AD cmdlets an admin finds a shortcut in Administrative Tools. To use the Server Manager ones he has to import a module. Exchange Management Shell has a shortcut in folder under All Programs.
Then working with them. An Exchange admin is familiar running cmdlets like:
get-mailbox
get-exchange server
Now he gets Server 2008 R2 and wants to use the AD cmdlets:
get-aduser -> error message
How hard was it to make them assume 'all' when no parameters are submitted? Now the admin can run get-mailbox for Exchange but has to type get-aduser -filter * to get basically the same result.
Do you want me to continue about the all System Center products and explain how the teams all took their own approach to implement PowerShell? :) |
| Mark Minasi |
Posted - 03/06/2010 : 2:04:50 PM
Resistance is futile, PoSH will assimilate you!<g> |
| Jazzy |
Posted - 03/06/2010 : 07:27:27 AM
quote:
Originally posted by Mark Minasi
You guys have to attend my sessions more often; I covered this 18 months ago.<g>
Blogged about it 18.5 months ago. :)
quote:
Jetze, the easy way to use either the AD or Server Manager powershell cmdlets is to load them in your PS profile. And if you like, build an alias on any command and it can become much shorter.
I'm not an systems administrator so I work on a lot of different systems. Cool advice though. Don't get me started about them AD cmdlets, BTW... |
| Mark Minasi |
Posted - 03/06/2010 : 07:02:28 AM
You guys have to attend my sessions more often; I covered this 18 months ago.<g>
Jetze, the easy way to use either the AD or Server Manager powershell cmdlets is to load them in your PS profile. And if you like, build an alias on any command and it can become much shorter.
Joe, I think Microsoft realized that servermanagercmd was a nice tool (if incomprehensible XML-wise) but because they unwisely built it to require .NET they needed a parallel and different tool for Server Core (ocsetup and oclist), which was blasted annoying. (Which leaves open the question, "since they put .NET on Server Core in R2, why not just put servermanagercmd on Server Core?" My guess is the requirement for PowerShell in the Common Engineering Criteria.) |
| joe_elway |
Posted - 03/06/2010 : 03:10:04 AM
I'd guess MS is serious about it. Everytime you run the command it tells you in a long statement that you shouldn't use it anymore. |
| wobble_wobble |
Posted - 03/05/2010 : 5:53:45 PM
quote:
Originally posted by JSCLMEDAVE
"Servermanagercmd.exe is deprecated, and is not guaranteed to be supported in future releases of Windows. We recommend that you use the Windows PowerShell cmdlets that are available for Server Manager."
Hopefully "you" (was not me) have not wasted about two months learning this...
Just in case you missed these -
"Servermanagercmd is deprecated, and is not guaranteed to be supported in future releases of Windows. Ah, Servermanagercmd, we hardly knew ye ..."
Installing, Managing and Troubleshooting Windows Server 2008 R2
http://www.minasi.com/08r2class/
Control Windows Features with DISM - The new feature-management tool Servermanagercmd.exe in Windows 7 and Windows Server 2008 has its pros and cons
http://www.windowsitpro.com/article/utilities/control-windows-features-with-dism.aspx
7/12/2009
Windows Server 2008 R2 Server Manager
http://joeelway.spaces.live.com/blog/cns!2095EAC3772C41DB!2606.entry
Servermanagercmd
Updated: August 12, 2009
http://technet.microsoft.com/en-us/library/ee344834(WS.10).aspx
I have to ask for no other reason than to stir it, but is this deprecated in the same way as WINS has been deprecated?
To quote Mark
'Yup, WINS, your number is up, but its OK, its a pretty large number'
And is this the same command that Ex2010 wants you to run to remotely manage other DC's? And can multiple Exchange Servers exist without WINS?
Of course, it could be that my brain is addled by drink and US immigration requirements! |
| Jazzy |
Posted - 03/05/2010 : 12:16:41 PM
quote:
...the confusingly named Get-WindowsFeature cmdlet:
Disagree. I never understood the distinction between roles, features and role services. I prefer to manage them all in the same way and preferably with no more cmdlets than absolutely necessary. |
| Jazzy |
Posted - 03/05/2010 : 12:12:03 PM
I used servermandercmd.exe a lot, in particular the -ip switch to use an imput file. The PowerShell cmdlets are very easy to use, but still I use Servermanagercmd.exe now and then, because it's less typing. Compare:
servermanagercmd -i telnet-client
And:
Import-Module ServerManager
Add-WindowsFeature telnet-client |
| JSCLMEDAVE |
Posted - 03/05/2010 : 12:09:29 PM
Sweet! Thank you for pointing that out Aidan.
"The PowerShell modules related to Server Manager are not loaded by default. Run this command to load them:"
PS C:\Users\Administrator> import-module Servermanager
"To display what roles and features you have installed, you run the confusingly named Get-WindowsFeature cmdlet:"
PS C:\Users\Administrator> get-WindowsFeature
|
| joe_elway |
Posted - 03/05/2010 : 11:51:12 AM
The powershell alternatives are pretty similar and are covered in the Mastering Windows Server 2008 R2 book (chapter 2). servermanagercmd still works in R2 but you're better off using the PowerShell cmdlets on R2. |
