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.
  • Posts

    • Hello police? I'd like to report a murder.
    • Ventoy 1.1.15 is out.
    • Win11Debloat 06.24.2026 by Razvan Serea Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. All changes made by Win11Debloat can be easily reversed, and most removed apps can be restored via the Microsoft Store. A full guide on how to undo the changes is available here. Win11Debloat features: Below is an overview of the key features and functionality offered by Win11Debloat. Please refer to the wiki for more information about the default settings preset. Remove a wide variety of preinstalled apps. Click here for more info. Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads. Disable tips, tricks, suggestions & ads across Windows. Disable Windows location services & app location access. Disable Find My Device location tracking. Disable 'Windows Spotlight' and tips & tricks on the lock screen. Disable 'Windows Spotlight' desktop background option. Disable ads, suggestions and the MSN news feed in Microsoft Edge. Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely. Disable & remove Microsoft Copilot. Disable Windows Recall. Disable Click to Do, AI text & image analysis tool. Prevent AI service (WSAIFabricSvc) from starting automatically. Disable AI Features in Edge. Disable AI Features in Paint. Disable AI Features in Notepad. Disable the Drag Tray for sharing & moving files. Restore the old Windows 10 style context menu. Turn off Enhance Pointer Precision, also known as mouse acceleration. Disable the Sticky Keys keyboard shortcut. Disable Storage Sense automatic disk cleanup. Disable fast start-up to ensure a full shutdown. ...and more. Once you’ve downloaded the Win11Debloat file (Get.ps1), just follow these quick steps: Locate the Get.ps1 script file. Right-click the file and select Run with PowerShell from the context menu. If prompted by User Account Control (UAC), select Yes to grant the script the necessary administrative permissions. Win11Debloat 06.24.2026 changelog: With this release, the legacy app list generator and CustomAppsList file support is removed. This only affects users using legacy command-line methods. More info here: #664 Features & Improvements Clean up styling to better match Windows fluent design guidelines by @Raphire in #638 Add GPO override warning alert and WhatIf dry-run previews by @HetCreep in #611 Disable telemetry-related scheduled tasks under Microsoft\Windows by @HetCreep in #615 Guard against loading, saving & executing undefined features by @Raphire in #665 Simplify Window management & update minimum window sizes by @Raphire in #671 Update start menu backup/restore with timestamped filenames by @Raphire in #672 Clean up feature execution logic for readability by @Raphire in #641 Clean up & improve app removal methods, remove legacy CLI app removal methods by @Raphire in #662 Remove support for CustomAppsList file format, including -RemoveAppsCustom and -RunAppsListGenerator parameters Update CLI app removal to use newer app removal methods Drop support for sunset apps (Fitbit, Shazam, Twitter, Viber, Wunderlist, XING) and Plex Fix removal of Microsoft Copilot Fixes Fix: Replace P/Invoke dynamic DLL imports with WPF native methods to fix temp DLL access-denied errors by @Raphire in #661 Fix Start Menu apps not being set correctly for all users when running script for other user by @Raphire in #637 Fix store suggestions not getting disabled correctly for all users when running as other user by @Raphire in #642 Fix: Respect Feature min/max version for comboboxes by @Raphire in #639 Fix: Don't treat AllUsers/CurrentUser as a username at startup by @HetCreep in #647 Fix: treat dismissed unsafe-removal confirmation as decline by @HetCreep in #651 Fix: Surface runspace errors instead of swallowing them in GUI mode by @HetCreep in #655 Fix: Correct sub-key path matching in backup allow-list validation by @HetCreep in #645* Fix: Detect WinGet uninstall failures by exit code, not English text by @HetCreep in #658 Fix: Detect installed OneDrive in the "Only show installed" filter by @HetCreep in #656 Download: Win11Debloat 06.24.2026 | Open Source View: Win11Debloat Home Page | Screenshots 1| 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Age of Empires Mobile PC Version The Band The Show The Movie
  • Recent Achievements

    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      416
    2. 2
      +Edouard
      173
    3. 3
      PsYcHoKiLLa
      125
    4. 4
      Michael Scrip
      77
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!