Recommended Posts

I disagree. Skinning not using much of resources. Glass will not using much of resources as well, only need is good GPU. Load of GPU is not affecting working of server function.

After all, even Gnome and KDE have skinning.

586325144[/snapback]

Who puts a graphics card with a good GPU in a server? Most will be headless or use integrated graphics. There is no point paying for a good graphics card on a server, thats not what servers are designed for.

hmm...

Look at this attachment:

I wish microsoft would make server installs like linux,

where you can choose what service's you need

now you get all this with a default install.. :no:

586336759[/snapback]

This is just a list of available services, have you actually checked to see which are running ? :rolleyes:

Jason, I know you were looking for information regarding Active Directory in Longhorn Server Beta 1. I haven't seen a whole lot about it, but I did find this on the TechNet site:

Active Directory

This information about known directory services issues applies only to Windows Server "Longhorn" beta 1.

? You must prepare your Active Directory forest and domain with Windows Server "Longhorn" beta 1 updates prior to promoting your first Windows Server "Longhorn" domain controller into an existing environment. Use the Windows Server "Longhorn" beta 1 version of the Active Directory Preparation Tool (adprep) located in %WINDIR%\System32\Adprep to prepare the environment. For information about how to use Adprep, see the Microsoft Web site.

Important:  The Active Directory Forest and Domain Schema updates for this beta 1 release of Windows Server "Longhorn" are not compatible with subsequent Windows Vista versions of Windows. If you prepare the environment with this version of Adprep, you will not be able to upgrade a Windows Server "Longhorn" beta 1 environment to any future beta or release version of Active Directory.

? You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) on server core installations. Instead, use the unattended version of dcpromo (Dcpromocmd.exe) to install or remove the domain controller role on servers running a server core installation. Using Dcpromocmd.exe requires an answer file. For more information, see the Microsoft Windows Server "Longhorn" Beta 1 Server Core Step-By-Step Guide on the Microsoft Connect Web site.

? You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) to promote a read-only domain controller. Instead, use the unattended version of dcpromo (Dcpromocmd.exe). For more information, see the Read-Only Domain Controller Step-by-Step Guide on the Microsoft Connect Web site.

? When you promote a server core installation to the domain controller role in a new forest and domain, Domain Name System (DNS) is not installed, even if you elect to install it during the promotion. Instead, you must configure DNS manually after you have installed the domain controller role. To enable and start the DNS Server service in Windows Server "Longhorn" beta 1, run Dnsserverrole.cmd from a command line.

More can be read by going to http://www.microsoft.com/technet/windowsvista/relnotes.mspx

I was wondering the same thing. The last version I saw and have is the LongHorn 3671.x86fre.Lab06_N.020821-1724 build which is a little old now!

But someone should install the new version and post pics for all of us not part of the beta.

BTW: I have two versions of that very old build the ads and the pro

586301445[/snapback]

Dont remember seeing any screenshots of this build...

Wow, the server is not for desktop crap again? Hey, look, I was on a Microsoft job interview last week, do you know what these guys used on their desktops? Windows Server 2003. Now go away.

586339285[/snapback]

Some MS devs swear by Server 2003, but just as many use XP.

One thing that remains to be seen about Longhorn...

Server 2003 is compelling as a workstation OS largely because it's newer than XP Pro (and by newer, I mean running a newer NT kernel and newer system services - like IIS 6.0) and also because it has more flexible admin-mode TS.

If the Vista client and server are both based on NT 6.0, then I think the server edition won't have the same appeal to many that Server 2003 does today. However, if it follows an XP/2003 like cycle and is released later as Windows NT 6.1, that arrangement may continue.

Longhorn Server will follow the same scheme as with XP again. 6 months more development than the client.

586355526[/snapback]

Agreed, I forgot that the schedule had been made public. Especially with the Monad comments the other day, saying that it won't ship with Vista but might ship with Longhorn Server...

With the lined-up Beta 1 releases I'd say it looks like they're following the XP development path...

As I recall, after beta 2, XP went to RCs, while the next release for Server was Beta 3.

  • 2 weeks later...
Some MS devs swear by Server 2003, but just as many use XP.

One thing that remains to be seen about Longhorn...

Server 2003 is compelling as a workstation OS largely because it's newer than XP Pro (and by newer, I mean running a newer NT kernel and newer system services - like IIS 6.0) and also because it has more flexible admin-mode TS. 

If the Vista client and server are both based on NT 6.0, then I think the server edition won't have the same appeal to many that Server 2003 does today.  However, if it follows an XP/2003 like cycle and is released later as Windows NT 6.1, that arrangement may continue.

586343645[/snapback]

A great reason to run windows server 2003 instead of xp is asp.net development. Its much easier / better to run the server locally and IIS in xp isn't the same version.

  • 2 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.