Thursday, February 12, 2009

Windows Server 2008: Active Directory Domain Services Auditing Capabilities Explained

Active Directory Domain Services Auditing has remained fairly consistent since the first release of Active Directory in Windows 2000 Server. However, Microsoft has introduced new Active Directory Domain Services auditing capabilities in Windows Server 2008. Active Directory Domain Services auditing in Windows Server 2008 provide more granular auditing capabilities and more control.

This article takes a deeper look at the new Active Directory Domain Services auditing capabilities in Windows Server 2008.

New Default Auditing Settings in Group Policy

Windows 2000 Server and Windows Server 2003 enabled auditing for a number of policies by default. However, Windows Server 2008 does not define these global audit settings by default. These settings are instead defined by using the new auditing subcategories. This may seem as though auditing is not configured by default, however this is not the case. The configuration of the global audit settings is inherited by the subcategories below that global audit setting. Therefore, Microsoft chose to configure specific subcategories by default, which is covered in the next section.

New Auditing Subcategories

As previously mentioned, Windows Server 2008 introduces auditing subcategories. The following table shows the subcategories below each global audit setting, as well as the default configuration for each audit subcategory.


Global Audit Setting

Subcategory

Default Setting

Audit Account Logon Events

Kerberos Service Ticket Operations

Success

Other Account Logon Events

No Auditing

Kerberos Authentication Service

Success

Credential Validation

Success

Audit Account Management

Computer Account Management

Success

Security Group Management

Success

Distribution Group Management

No Auditing

Application Group Management

No Auditing

Other Account Management Events

No Auditing

User Account Management

Success

Audit Process Tracking

Process Termination

No Auditing

DPAPI Activity

No Auditing

RPC Events

No Auditing

Process Creation

No Auditing

Audit Directory Service Access

Directory Service Changes

No Auditing

Directory Service Replication

No Auditing

Detailed Directory Service Replication

No Auditing

Directory Service Access

Success

Audit Logon Events

Logoff

Success

Account Lockout

Success

IPsec Main Mode

No Auditing

IPsec Quick Mode

No Auditing

IPsec Extended Mode

No Auditing

Special Logon

Success

Other Logon/Logoff Events

No Auditing

Logon

Success and Failure

Audit Object Access

File System

No Auditing

Registry

No Auditing

Kernel Object

No Auditing

SAM

No Auditing

Certification Services

No Auditing

Application Generated

No Auditing

Handle Manipulation

No Auditing

File Share

No Auditing

Filtering Platform Packet Drop

No Auditing

Filtering Platform Connection

No Auditing

Other Object Access Events

No Auditing

Audit Policy Change

Authentication Policy Change

Success

Authorization Policy Change

No Auditing

MPSSVC Rule-Level Policy Change

No Auditing

Filtering Platform Policy Change

No Auditing

Other Policy Change Events

No Auditing

Audit Policy Change

Success

Audit Privilege Use

Non Sensitive Privilege Use

No Auditing

Other Privilege Use Events

No Auditing

Sensitive Privilege Use

No Auditing

Audit System Events

Security System Extension

No Auditing

System Integrity

Success and Failure

IPsec Driver

No Auditing

Other System Events

Success and Failure

Security State Change

Success



Source: http://www.enterpriseitplanet.com/networking/features/article.php/3797931

Wednesday, February 4, 2009

SBS 2008 to SBS 2008 Migration Fails When "Windows SBS User Policy" Edited

Windows Small Business Server 2008 creates a group policy called "Windows SBS User Policy", one of the tasks of this group policy is to add a few shortcuts (OWA, RWW, and WSS) to IE on SBS clients. If this list is modified AND you attempt a SBS 2008 to SBS 2008 migration the migration will irrecoverably fail. You will receive this following installation issue and be unable to complete the migration:

The installation of Windows Small Business Server 2008 cannot finish.

At this point, you must restore the original server from backup and completely start the migration process over. To avoid this issue please complete the following steps prior to a SBS 2008 to SBS 2008 migration:

Note: This only needs to be done if the policy has been edited. If you're not sure, there is no harm in doing these steps as a precaution.

  1. Open gpmc.msc and edit the "Windows SBS User Policy".
  2. Navigate to User Configuration -> Policies -> Windows Settings -> Internet Explorer Maintenance -> URLs.
  3. View the properties of Favorites and Links.
  4. Make a note of all the Favorites and Links (This has likely been customized from the default).
  5. Remove all the Favorites and Links and save the policy.

Once you complete the migration, the favorites for OWA, RWW and Companyweb will be automatically recreated. You will then have to manually re-add your custom URLs.

SBSSetup.log Errors:

[908] 080925.155308.3044: Setup: Task ConfigureIE succeeded.
[908] 080925.155308.3200: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureIE" Task or the "NET" TaskProcessor threw an Exception during the ITaskProcessor.Run() call:System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility._normalFavoritesEX()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility..ctor()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility.DelIEFavorites(String keyName)
at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureIE.Run(ITaskDataLink DataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskProcessors.NetTaskProcessor.Run(Task currentTask, ITaskDataLink dataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink, IDictionary`2 taskProcessorMap)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName)

[908] 080925.155308.3200: Setup: An error was encountered on the TME thread: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility._normalFavoritesEX()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility..ctor()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility.DelIEFavorites(String keyName)
at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureIE.Run(ITaskDataLink DataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskProcessors.NetTaskProcessor.Run(Task currentTask, ITaskDataLink dataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink, IDictionary`2 taskProcessorMap)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName)
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter._RunTasks(Object sender, DoWorkEventArgs e)
[2228] 080925.155308.5384: Setup: _UnhandledExceptionHandler: Setup encountered an error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: The TME thread failed (see the inner exception). ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility._normalFavoritesEX()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility..ctor()
at Microsoft.WindowsServerSolutions.ClientSetup.IEUtility.DelIEFavorites(String keyName)
at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureIE.Run(ITaskDataLink DataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskProcessors.NetTaskProcessor.Run(Task currentTask, ITaskDataLink dataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink, IDictionary`2 taskProcessorMap)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName)
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter._RunTasks(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter.TasksCompleted(Object sender, RunWorkerCompletedEventArgs e)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardFrameView.Create()
at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardChainEngine.Launch()
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass._LaunchWizard()
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.RealMain(String[] args)
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.Main(String[] args)
[2228] 080925.155308.5696: Setup: Removed the password.
[2228] 080925.155308.5696: Setup: Deleting scheduled task at path Microsoft\Windows\Windows Small Business Server 2008 with name Setup
[2228] 080925.155308.5852: Setup: Removed SBSSetup from the RunOnce.

Source & inspiration: http://blogs.technet.com/sbs/archive/2008/12/16/sbs-2008-to-sbs-2008-migration-fails-when-windows-sbs-user-policy-edited.aspx

Friday, January 30, 2009

Windows Home Server for Small Business

(Business Wire) LPI Level Platforms Inc, the global leader in remote monitoring and management software for solution providers and managed services providers today announced that the Small Office/Home Office (SOHO) market is now “open for business” with Microsoft’s Windows Home Server.

While the millions of SOHO businesses have the greatest need for outsourced IT, cost and technology limitations have made this an elusive target for managed services providers.

With Level Platforms award-winning Managed Workplace installed on a Windows server, solution providers can now deliver end-to-end remote management of workgroup networks including monitoring of all devices (servers, PCs, network devices, printers, IP telephony, etc.), all applications running on Windows devices, alerting, full asset management, remote control, patch management, back up and security, extensive reporting, local storage and much more at a very low cost easily affordable to SOHO businesses.

“With this announcement we are radically expanding the size of their available market and bringing the benefits of managed services to millions of businesses that were not previously accessible to the service provider community.” said Peter Sandiford, CEO Level Platforms.

“By adding the Windows Home Server as a supported platform for Managed Workplace, Level Platforms has opened the doors to a hugely underserviced and important segment of the business market.” said Aaron Booker, President of Hardlines, a Washington-based solution provider focused on the small business market.

“We are excited to work with Level Platforms to extend the value of Windows Home Server to the Small Office/Home Office market,” said Charlie Kindel, General Manager, Windows Server Solutions Group, Microsoft (NASDAQ:MSFT). “This solution will help Microsoft Partners introduce the benefits of Windows Server technology to a large and important market segment establishing a solid foundation for improved performance and reliability today and growth for the future.”

Source: http://www.earthtimes.org/articles/show/windows-home-server-for-small-business,697081.shtml

Friday, January 23, 2009

Red Hat Gives Boost To Virtual Server Support

Red Hat decide to give some boost to virtual server support. Red Hat's Enterprise Linux 5.3 release is a sign of the times, both in terms of the growing importance companies are placing on the scalability of virtual environments and as an example of the maturity of enterprise Linux.

Launched Tuesday, Red Hat Enterprise Linux 5.3 supports virtual servers with up to 32 virtual CPUs and 80 GB of memory, and includes new performance-boosting features such as Hugepage memory andIntel Extended Page Tables. Red Hat has also bumped physical server support to 126 CPUs and 1 TB of main memory.

Red Hat Enterprise Linux 5.3 also adds support for Intel Core i7 processors and OpenJDK, the official open-source core of the Java SE specification. The integration of OpenJDK marks the culmination of a push that began more than 18 months ago to shift Red Hat's development resources away from in-house projects and toward OpenJDK.

In November 2007, Red Hat signed Sun's OpenJDK license agreement and licensed Sun's Java Standard Edition (SE) technology compatibility kit, essentially paving the way for Red Hat to develop an officially compatible open-source Java Development Kit for Red Hat Enterprise Linux.

While the new additions to Red Hat Enterprise Linux 5.3 are noteworthy, the new release shows that Linux purveyors are more focused on performance and new hardware and standards support than they are on adding game-changing new features, according to Gordon Haff, a principal IT adviser at research firm Illuminata.

Source:http://www.crn.com/software/212901511

Friday, January 16, 2009

How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer

Support personnel and network administrators can use the Windows 2000 Support Tools to help manage their networks and troubleshoot problems. Note that you should install the Windows 2000 Support Tools before you contact Microsoft for support. This article describes how to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer.

Install Windows 2000 Support Tools

To install the Windows 2000 Support Tools:-

1. Start Windows 2000. Note that you must log on as a member of the administrator group to install these tools.
2. Insert the Windows 2000 CD-ROM into your CD-ROM drive.
3. Click Browse this CD, and then open the Support\Tools folder.
4. Double-click Setup.exe, and then follow the instructions that appear on the screen.

The following tools are included with Windows 2000:

Acldiag.exe
Adsiedit.msc
Apcompat.exe
Apmstat.exe
Browstat.exe
Clonepr.dll
Dcdiag.exe
Depends.exe
Dfsutil.exe
Dnscmd.exe
Dommig.doc
Dsacls.exe
Dsastat.exe
Dskprobe.exe
Dumpchk.exe
Filever.exe
Gflags.exe
Kill.exe
Ksetup.exe
Ktpass.exe
Ldp.exe
Memsnap.exe
Movetree.exe
Msicuu.exe
Msinfo32.exe
Msizap.exe
Netdiag.exe
Netdom.exe
Nltest.exe
Pmon.exe
Poolmon.exe
PPTP Ping
Pviewer.exe
Reg.exe
Remote.exe
Repadmin.exe
Replmon.exe
Rsdiag.exe
Rsdir.exe
Sdcheck.exe
Search.vbs
SIDWalker
Snmputilg.exe
Tlist.exe
W2000msgs.chm
Windiff.exe
Winrep.exe
Wsremote.exe

Source: http://support.microsoft.com/kb/301423

Wednesday, January 14, 2009

Online Server Support Services For your Small Businesses

Are you offend of dealing with pesky server problems, always displaying messages such as 'Cannot create a connection to data source' or 'login failed for user 'username' or other errors such as 'login failed for user 'not authority'?

Resolve all these server issues once and for all with the help of professional System Engineers? You can easily find them through leading online technical support resources. They offer critical server support through remote sessions. Entirely focusing on leading technology, these expert technicians give their best to leverage the best out of their technical knowledge and skills to cater your server support requirements.

By using different technologies, tools and products, these system engineers diagnose your server to determine errors and troubleshoot all issues and faulty items causing execution failure. And this all is done right away without wasting any time. Consequentially, they plan the maintenance of swap-out for the most convenient time.

Online server support services are gaining in popularity primarily with small businesses. There are several different factors pushing popularity of online server support services with major being 24x7 availability and experts' help at the most affordable prices.

System Engineers working with online technical support resources are known to follow a precise as well as meticulous approach to cut down the cost of IT support services and increase the overall efficacy of services. This allows customers to work out their IT competencies to achieve business objectives.

Exclusive online server support resources like iYogi offer remote monitoring and management for all components of your server infrastructure, including systems at the Operating System level, custom applications, databases, networks, and the Internet. You can also ask for personalized solutions to fulfill your unique business needs.

Moreover, you can ask your support technicians for tweaks to maintain an efficient server network. It is always recommended to not to overload your server with too many photos loading in web pages especially those with large sizes.

Always clean up your blog mess on regular basis. Remove widgets and other files in your header, sidebar and footer that are no longer useful. All such tips will help you to cut load on your server and upload your web pages fast.

Source: http://ezinearticles.com/?Server-Support&id=1374938

Friday, January 9, 2009

SMB Powerhouse Windows Server 2008 R2 Beta Is Public

During yesterday's Microsoft keynote at CES, Steve Ballmer announced the release of the public beta of Windows Server 2008 R2, which is a midway release between its major server releases. This is a philosophy that the Windows Server team at Microsoft adopted since Windows Server 2003. R2 beta will be available for download on the WinServer R2 web site.

While R2 arrives with myriad new features, there are two key areas that are of great interest to IT generalists and small VARs that cater to the SMB. First, a new DirectAccess feature eliminates the need for VPN connectivity by providing seamless intranet based connectivity to Windows 7 clients from remote locations. DirectAccess will do away with the need to buy any VPN appliance. What's more, administrators will be able to manage remote computers just like computers inside corporate intranets. For VARs, DirectAccess spells a boom in new business revenue. VARs can offer managed services directly from their networks.

Windows Server 2008 R2

In R2, Microsoft also changed some of the network plumbing and underlying protocols to increase the efficiency of file transfers and improve remote connectivity with Hyper-V. As a result, the old Terminal Services will no longer be supported.

R2 provides a new Remote Desktop service using a new Virtual Desktop Infrastructure (VDI). In a R2 VDI environment, remote computers will be able to connect to virtual desktops, instead of physical machines. Hyper-V's virtualization technology makes it looks seamless. From the point of view of users, they won't be able to distinguish if the virtual desktops are virtual or installed on physical hardware.

While this might sound too esoteric for many small businesses to deploy, in actuality, it is not. I've worked with Hyper-V in the past and found it extremely easy to use. Small business will be able to reduce operational costs because the desktops exist in the VDI environment (a server box). You won't be rolling your eyes back when you see the price. It's all included in the Windows Server 2008 license.

Source: http://blogs.pcmag.com/atwork/2009/01/ces_2009_smb_powerhouse_window_1.php