Scalable Networking Pack Rollup Released


De rollup package vind je hier: KB950224

Meer informatie over SNP vind je hier: http://www.microsoft.com/technet/network/snp/faq.mspx

Verder kwam ik de volgende quote tegen:

As more companies deploy Windows 2008 and Vista, it is crucial, or in my opinion, critical that this hotfix be applied to all Windows 2003 servers that may communicate with these operating systems. One of the main reasons is a new feature called TCP auto-tuning which makes use of RSS to expand and shrink the sizes of your TCP window to increase/decrease throughput based on current network load. This feature greatly increases throughput on your network, but if there is an underlying problem with the network card driver or any of these features between disparate systems, you may experience slower than normal network performance. The good news is that the Chimney feature is disabled by default in Vista/Windows 2008.

Bron: http://blogs.technet.com/mikelag/archive/2008/08/28/scalable-networking-pack-rollup-released.aspx

LDAP Query


In mijn omgeving werken we nu nog met twee verschillende loginscripts. Ik wilde graag weten welke gebruikers die nog enabled waren het oude loginscript aangekoppeld hadden. Dit kun je doen door de volgende LDAP query uit te voeren in Active Directory Users and Computers.

 

De onderstaande query geeft alle users weer met het loginscript login.bat en de accountstatus op enabled

(objectCategory=person)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2)(scriptPath=login.bat))

 

De volgende LDAP query doet bijna hetzelfde als de bovenstaande alleen geeft deze de personen terug met de accountstatus op disabled

(objectCategory=Person)(objectClass=User)(userAccountControl:1.2.840.113556.1.4.803:=2)(scriptPath=login.bat)

 

Een LDAP query ziet er dan als volgt uit:

image

Geholpen door het volgende KB artikel: KB827754

Whitepaper: VMware and VSS: Application Backup and Recovery


Veeam schrijft het volgende:

More and more organizations are choosing VMware Infrastructure to virtualize their mission‐critical applications (Active Directory, Exchange, SharePoint, SQL Server) to create a flexible, easily administered virtual infrastructure.
Virtual machines (VMs) and any applications they contain must be protected against failure. Typically, in the virtual world, this is done by performing an image‐level backup of the whole machine (for instance, using VMware Consolidated Backup). This method results in what is known as a crash‐consistent image. Restoring a crash‐consistent image is essentially equivalent to rebooting a server after a hard reset. For operating systems, this has not been an issue, since they can easily handle this type of activity. For database applications as well as for applications featuring replication, however, such a restore will often result in lost data, data corruption, or application failure.
To illustrate this concept, let’s review the consequences of using different VM disaster recovery methods for one of the most common mission‐critical applications: a Microsoft Active Directory domain controller (DC). Depending on the solution used, the following results will be achieved:

image

Download de PDF hier: VMwareandVSS-ApplicationBackupandRecovery.pdf

Backup Exec: Snapshot provider error (0x8007000E): Ran out of mem


Sinds ik SP2 op de SQL server had geïnstalleerd, kreeg ik de onderstaande foutmelding in mijn Backup Exec log file.

Click an error below to locate it in the job log


Backup- SQL1 
AOFO: Initialization failure on:
\\SQL\Shadow?Copy?Components.
Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0x8007000E): Ran out of memoryCheck the Windows Event Viewer for details.

Dit probleem kun je oplossen door de hotfix te bestellen die vermeldt word in het volgende KB document: KB940239

Microsoft: Health Checks on Domain Controllers


Brian W. McCann heeft een korte post gemaakt over Health Checks on Domain Controllers.

Hieronder zie je de tools die hij beschrijft:

Dcdiag.exe /v >> c:\temp\pre_dcdiag.txt
This is a must and will always tell you if there is trouble with your DCs and/or services associated with it.

Netdiag.exe /v >> c:\temp\pre_Netdiag.txt
This will let me know if there are issues with the networking components on the DC. This along with the post test also is a quick easy way to ensure the patch I just installed is really installed (just check the top of the log)

Netsh dhcp show server >> c:\temp\pre_dhcp.txt
Some may not do this but I’ve felt the pain of a DHCP server somehow not being authorized after a patch. This allows me verify the server count and names.

Repadmin /showreps >> c:\temp\pre_rep_partners.txt
This shows all my replication and if it was successful or not. Just be aware that Global Catalogs will have more info here than a normal domain controller.

repadmin /replsum /errorsonly >> c:\temp\pre_repadmin_err.txt
This is the one that always takes forever but will let you know who you are having issues replicating with.

Bron: http://www.adminprep.com/articles/default.asp?action=show&articleid=101

VMware: The DB user entered does not have the required permissions


Bij het vers installeren van VirtualCenter 2.5 kreeg ik bij het configureren de volgende foutmelding:

image

Dit kwam omdat ik bij de gebruiker in SQL 2000 geen ‘Server Roles’ had toegevoegd. De volgende Roles heb je nodig voor een succesvolle installatie:

  • System Administrators
  • Server Administrators
  • Database Creators (ik weet niet zeker of deze erbij moet, dit heb ik voor de zekerheid gedaan).

sql_rechten

Meer informatie over het installeren / upgraden van je VC Database vind je hier:

VM ID: 1003346

VM ID: 1003610

Considerations when hosting AD DC in virtual environments


KB888794:  Considerations when hosting Active Directory domain controller in virtual hosting environments

 

In het bovenstaande KB artikel tref je ook nog de volgende artikelen aan:

KB875495: How to detect and recover from a USN rollback in Windows Server 2003.

KB885875: How to detect and recover from a USN rollback in Windows 2000 Server.

KB897615: Support policy for Microsoft software running in non-Microsoft hardware virtualization software

Citrix: Username.Domain folders on the TSProfile Share


Het kan voorkomen dat je de onderstaande tsprofiles tegen komt op je TSProfile share. Meer informatie over hoe dit komt lees je in KB821929

UsernameDomain2

Ik vond een post van Robert Illing op het Citrix forum met de oplossing:

Apparently in SP1 they incorporated this hotfix – http://support.microsoft.com/?id=821929. If you look at the bottom if the hotfix it shows how windows looks at the terminal server roaming profiles.

We use \\server\username for our home drives and the \\server\username.domain caused us problems. The thing is windows will actually attempt \\server\username, but the user has to have full control on their profile. They also need to be the owner of the folder. If they are not the owner, windows will create a NEW profile for them using username.domain which created tons of profiles on our san.

There is a work around on the ownership problem. As we scripted our whole solution, and went about to go in and change ownership on thousands of profiles. If you create a GPO and go to Computer Configuration, Administrative Templates, System, User Profiles, then select “Do not check for user ownership of roaming profiles folder”. This will ignore the ownership of the profile.

So to clarify once you apply that GPO. You should be able to use \\server\username as long as the user has full control on their profile.

Op de policy met GPMC.msc en ga naar Computer Configuration – Administrative Templates – System –  User Profiles daarna enabale je de volgende optie Do not check for user ownership of roaming profiles folder

UsernameDomain

Citrix: Licensing error EventID 1028


Ik starte vandaag een oude VM op en wilde verbinding maken naar de Citrix omgeving. Dit lukte niet. Ik kreeg de onderstaande error.

License_Error

De volgende EventID werd in de eventlog weggeschreven op de terminal/citrix server.

eventid1028

De oplossing voor dit probleem was het verwijderen van de MSLicensing key. Dit doe je via Regedit op de client en blader dan naar de key: HKLM\SOFTWARE\Microsoft en verwijder de key MSLicensing.

 License_Error_regedit

De oplossing kwam van Super Pippo op het Citrix forum: http://support.citrix.com/forums

Meer informatie over TSServer Licensing vind je in het volgende KB document: KB823313