Say NO to the Microsoft Office format as an ISO standard

[esteel]

There is no need to argue.. of cource a massive windows installation is easy to manage as long as you live in the world of being used to be told by microsoft exactly what to do, and simply accept that "this cannot be done" for the simplest taksk.

emphasis mine..
last time i tried on a xp media edition laptop i couldn't even put the 'always visible' taskbar from the bottom of the screen to the top of the screen! New windows did popup UNDER it makeing it hard to impossible to move them as the taskbar was hiding the window top so couldn't move it with the mouse and alt-space, move does not work with all programs (putty for example can grap the alt key to transmit it via ssh). So i had to set the taskbar to automatically-hide so i could get to the window top and move it around.

Sure its a totally other thing as was discussed but it kinda shows how well-designed the windows ui is why should the other stuff be any better..

[7echno7im]

I never said SMS can only install msi's, scroll up. SMS can do sooo much more. I was just giving an example. SMS is also a reporting system, i can find make, model, serial number, bios revision, and anything about a machine via sms's reporting feature. It pulls hardware info from wmi and software from the OS.

SMS can do anything you tell it to, it is a deliverer, executer, reporter, tracker, monitor, not just and installer and definitely not just msi's.

And yes you can install thru logon scripts. Write a bacth or vbs or any scipt, have it execute on login by user or computer (via group policy editor) , simple, dirty, easy, pre-sms. You can chose a machine accoutn rather than a user account, thus having the rights to install. Plus, you can write the script tio do a 'run as'. PSEXEC is another good tool to use.

Certification does not always mean they possess the knowledge to manage a network. Depending on the cert. Some people just study answers for them, not learing best practices and concepts.

I agree that Novell Netware was good at the time, our entire network use to be novell/ipx/groupwise, as most were. It was a management nightmare, from logon scripts, file shares, accounts,mail accounts, aliases, etc... Everything was good for the time, but was not flexible to adapt to the market trends.

I am sorry that this thread veered so far away from it's original topic, it was not my intent.

[Dokujisan]

oh well... looks like OOXML got accepted by Massachusetts.

http://arstechnica.com/news.ars/post/20 ... oming.html

[tChr]

Office Open XML is a good thing and a clear improvement of Microsoft standrads, but its still a crappy half-done document, and should _not_ replace ODF as an ISO

[ai]

Who are the ones making the ODF and who are the ones that needs it? As I see it, even if OOXML gets accepted, I think many still will use the other standard. Or what am I missing? Don't have too clear picture of what those are in more general (market)-term.
And how does not people see what MS are trying to do? I think bribery... or something alike. Stupid people with no intelligence.

[Dokujisan]

OOXML Fails to Gain Approval in US

http://www.robweir.com/blog/2007/07/oox ... in-us.html

[tChr]

Who are the ones making the ODF and who are the ones that needs it? As I see it, even if OOXML gets accepted, I think many still will use the other standard. Or what am I missing? Don't have too clear picture of what those are in more general (market)-term.
And how does not people see what MS are trying to do? I think bribery... or something alike. Stupid people with no intelligence.

You are missing that MS is trying to make oosml replace odf as the standard,. (same ISO number among other things)