DaniWeb IT Discussion Community - Novell http://www.daniweb.com/forums/ en-US Sat, 21 Nov 2009 20:15:47 GMT vBulletin 60 http://www.daniweb.com/alphaimages/misc/rss.jpg DaniWeb IT Discussion Community - Novell http://www.daniweb.com/forums/ Novell Open Enterprise Server for Linux+ZENworks http://www.daniweb.com/forums/thread239940.html Fri, 20 Nov 2009 06:26:05 GMT Novell Open Enterprise Server for Linux+ZENworks ,that is 050-704, is the hot emerging test exam in recent years.
it aims to test the learners ablity to deal with linux+ zenworks .
here is some Q&A you may have a look at which may help you to some extend.
1.By default, the iPrint system uses port ________ to send non-secure print jobs. Answer:
A.PORT631
Correct:A
2.When migrating volumes from a NetWare server to an OES Linux server, which are
considerations you should keep in mind? (Choose 2.)
A.Open files on the source volume won't be migrated, by default.
B.The creation date of the files on your migrated volume will be reset to the current date.
C.Linux User Management must be disabled on the destination server before starting the migration.
D.If the source NetWare volume is part of a server cluster and it fails over during the migration, the Server
Consolidation utility can continue the migration process using a redundant server in the cluster.
E.The file ownership attribute is not preserved when migrating NetWare NSS volumes to OES Linux
volumes.
F.You will lose all trustee rights assignments when migrating a traditional NetWare volumes to OES Linux
NSS volumes.
Correct:A B
3.You've just completed an upgrade of a NetWare 5.1 server to OES NetWare. You now need to
install additional products. Which utilities can you use to do this? (Choose 2.)
A.iManager
B.Remote Manager
C.Deployment Manager
D.Novell Application Manager
E.The Install utility in the OES NetWare server GUI
Correct:C E
4.Your organization's eGuide service is installed on an OES Linux server with a DNS domain name
of da12.da.com. You've configured eGuide to use eDirectory as its LDAP directory service. Your
users need to access the eGuide service from their workstations using a web browser . What URL should they use to do this? Answer:
A.HTTP://DA12.DA.COM/EGUIDE
Correct:A
5.You're setting up an iFolder server in your network that will service 1800 users. The server uses a dual Pentium 4 CPU motherboard and a 500 GB RAID 3 storage array. The server is connected to workstations through a Gigabit twisted-pair Ethernet network. Does this system meet Novell's recommended design guidelines for iFolder?
A.Yes, all recommendations are met.
B.No, iFolder is not multiprocessor-enabled.
C.No, iFolder does not support RAID 3 storage devices.
D.No, a single iFolder server should serve a maximum of 1000 users.
E.No, iFolder should be implemented on a fiber-optic Ethernet network.
Correct:D
6.You're planning the deployment of a new Open Enterprise Server network. You will create a new eDirectory tree with the first OES server you install. Each server in the tree will function in a
specified role. You plan to install the following servers: . DA1. DA1 will be an OES Linux server that will run NCP Server and contain NSS volumes. . DA2. DA2 will be an OES Linux server that
will run NCP Server and NSS. It will also be used to create an iSCSI SAN using the other servers in the network. . DA3: DA3 will be an OES Linux server that will run NCP Server, NSS, and iFolder. .
DA4: DA4 will be an OES Linux server that will run NCP Server, NSS, and NetStorage. . DA5: DA5
will be an OES Linux server that will run iManager to provide remote management services for the entire network. Which server should be the first server installed in the eDirectory tree?
A.DA1
B.DA2
C.DA3
D.DA4
E.DA5
F.It doesn't matter which OES server is installed first in the eDirectory tree.
Correct:F
however more real questions you can visit passcert ]]> Novell honeybaby http://www.daniweb.com/forums/thread239940.html Microsoft Outlook Anywhere Setup http://www.daniweb.com/forums/thread220786.html Tue, 01 Sep 2009 00:54:43 GMT When setting up Outlook Anywhere in Exchange Server 2007, all the steps described in "Exchange Server 2007 End-to-End Scenario" are not enough. You need to run the following command in the Exchange Management Shell:

Get-AutodiscoverVirtualDirectory | set-AutodiscoverVirtualDirectory
-ExternalURL https://your-iis-server.yourdomain.c...todiscover.xml

Here "your-iis-server" is the IIS server name where you have your Exchange "AutoDiscover" Web application hosted.

Besides this extra step, all the steps described in "Exchange Server 2007 End-to-End Scenario" must be followed exactly. You can get to "Exchange Server 2007 End-to-End Scenario" by clicking on the root node in the left pane of the "Exchange Management Console". The "End-to-End Scenario" is on the second tab.

On the client side, as long as your local LAN setup works, you can leave it alone, even if you use domain names that are not publicly accessible since virtual RPC over HTTPS will take care of that automatically. All you need to do is to check the "Connect to Microsoft Exchange using HTTP", and setup "Exchange Proxy Settings". This is located in the email account setup dialog box. Click on "More Settings...", and then go to the "Connection" tab. Outlook Anywhere settings is at the bottom of this tab. Your Exchange server IIS external URL should be entered in the "Exchange Proxy Settings" dialog box as the proxy server URL.

One thing you should do is to keep all your authentication protocol consistent. If you choose to use NTLM, use it at every step. Otherwise use "Basic Authentication" everywhere. ]]> Novell tan00001 http://www.daniweb.com/forums/thread220786.html News Story The Late Great Mythical SCO http://www.daniweb.com/news/story220778.html Sat, 29 Aug 2009 21:24:56 GMT OK, I can't resist this whole SCO thing, since it has again raised its ugly head. My previous post on the subject the other day drew a lot of attention from a diverse gaggle of readers and commenters so I thought I'd go back to the well at least once more for good measure. Here's the real shocker in the whole SCO v. Everyone mess--they still think that they own Unix. Though they never produced proof in the past 6 or so years since the original lawsuit maelstrom began. They are so convinced that they own Unix, that they have it clearly stated so on their website.

Here is an excerpt and a link to that informative page:

Quote:
SCO owns all rights and ownership of the core UNIX operating system source code originally developed by AT&T/Bell Labs. SCO’s ownership includes system source code, including all versions and copies, SCO OpenServer, and substantial copyrights and source code to UnixWare. SCO is the exclusive licensor to UNIX-based system software providers.
Pretty ballsy, huh?

My original post from May 2008 explains that SCO doesn't own Unix, Novell does. Novell never transferred the copyright to them and Novell has proof. SCO purchased UnixWare from Novell, which is a standalone product but is not Unix in the pure and copyrighted sense of the word. It is a derivative thereof.

At this point, I'm not sure if it matters who owns Unix. It might not matter who holds the copyright, the license, or the original source code. Why does it not matter, you ask? In the Linux perspective, Linus wrote the Linux kernel off of Minix and publicly available code--plus original code of his own.

Not that anyone in this world is 100% above reproach but come on, Linux Torvalds is one smart cookie who doesn't need or desire to rip off anyone's source code.

Let's say for a moment that Linus had ripped off the source from SCO or whomever, would he still be able to update the kernel and include new code into it on his own? If he's too lazy to do his own coding, what makes anyone think that he would have continued the project for more than 15 years? It would have been far easier to admit his transgression, take a smack on the head and go about his business. He chose, instead, to continue his legitimate pursuit of the perfect operating system kernel and allow others to expand on his creation.

On the shoulders of giants, as Einstein once said.

SCO was once a great company. I loved SCO. It was everywhere. It was stable. It was awesome. But then Linux came along and took the world by storm and put SCO into a tailspin.

It doesn't have to be this way. Radios still exist. Trains still exist. Horses still exist. SCO can still exist too. It just can't have the same impact it used to have.

So, to SCO, you'll always be remembered as one of the finest operating systems in the history of computing--you had your day. Don't spoil it. It's like that last Rocky movie--OMG, just retire and let us remember you as you were. Don't embarrass yourself with this kind of Al Goresque recountism. Just go away quietly--or don't--find your niche again and rise from the ashes with renewed strength and vitality. But, please, please don't continue this path of lawsuit destruction. It isn't pretty. ]]> Novell khess http://www.daniweb.com/forums/thread220778.html <![CDATA[News Story SCO vs. Linux Again--You've Got to be Kidding.]]> http://www.daniweb.com/news/story220767.html Wed, 26 Aug 2009 20:03:58 GMT Just when you thought it was safe to return to those keyboards knowing that all is well with the world and the ownership of Unix is happy with its rightful owner, Novell; he's baaaack. I'm sure that I'm not the first to look at this latest news and say "WHAA? AGAIN? I thought we had this settled." But noooo, Linux arch nemesis SCO with the inimitable Darl McBride at the helm is at it again. I am so shocked at this latest attempt by the perhaps brain-damaged judges panel in the 10th U.S. Circuit Court of Appeals in Denver to continue this pointless battle over the ownership of the Unix copyright. Can they be serious? Apparently so.

I almost didn't bother posting about this when I saw it but I feel that I owe it to my loyal readers to weigh-in on this injustice and clear abuse of the legal system.

Has SCO not spent enough money on lawyers and legal fees? Do they absolutely just want to spend every last penny that they have on this?

What do they hope to gain, even if by some minute chance in hell that they win this time, from it? People have been so burned by this whole crazy lawsuit that the good name that was once SCO is now so tainted, no one will touch them. And, I'm forecasting that their remaining customer base will soon be nonexistent.

So, here's my final* take on the SCO v Linux issue:

To the Judges Panel of the 10th Circuit Court of Appeals: Guys, this was over in 2007. Have you nothing better to do than to reopen this wound? Come on, go play some golf or hit some tennis balls--it's time to retire.

To Darl McBride: Darl, I'm sorry that you don't own Unix. It sucks. Save your money, abandon the SCO operating system and just use Linux. Have yourself a frosty beverage and laugh at your former self for being so ridiculously out of line on this whole thing or perhaps seek out help for your condition--great progress is being made in this area.

To SCO's remaining Customers: Linux is a cool operating system that's free to use. There are several really good distributions from which to choose--please go try one or more of them. I also have some information that there's a little software company, a startup or something up in Washington state, called Microsoft. I hear they have a cool operating system that might work for you too.

To SCO's remaining Employees: Monster, Dice and HotJobs are convenient, online service companies. Check them out. They can help you.

Though I believe that what is legal and what is right are often diametrically opposed, I am hopeful that this will come to a quick resolution that is much, if not exactly, like the one in 2007.

*Unless SCO wins, then I'll have plenty to say about it. ]]> Novell khess http://www.daniweb.com/forums/thread220767.html