Bart's Weblog

Just a blog…

Archive for January, 2008

DC Locator Process in W2K, W2K3(R2) and W2K8

Posted by bartvdw on 2828/0101/2008

The best explanation I have ever found… The 3 blog articles below from Jorge explain you everything that is needed to know about the DC Locator Process in W2K, W2K3(R2) and W2K8!!

DC Locator Process in W2K, W2K3(R2) and W2K8 – PART 1
http://blogs.dirteam.com/blogs/jorge/archive/2007/06/30/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-1.aspx

DC Locator Process in W2K, W2K3(R2) and W2K8 – PART 2
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-2.aspx

DC Locator Process in W2K, W2K3(R2) and W2K8 – PART 3
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-3.aspx

Posted in Windows | Leave a Comment »

McAfee ePO: Duplicate MAC addresses

Posted by bartvdw on 2828/0101/2008

1 thing is sure: duplicate MAC addresses are a problem for ePO. Why? Simple: it uses the MAC address as unique identifier!

In short: if the Agent GUID is not found, the server uses the MAC address of the machine to verify against the database. If the MAC address is found, the existing database entry is updated with the new machine information. If the MAC address is not found, a new database entry is created and populated with the new machine information.

Result: duplicate MAC addresses are something you don’t want in combination with ePO.

Therefor be careful with cloning processes (same for Agent GUID). However this is not the only source of duplicate MAC’s… For example NLB servers share their MAC address. OK, not everybody runs NLB servers (I for instance prefer HLB configuration), I know!

What to do if you run a lot of NLB servers? Reconfigure ePO to not use the MAC address as unique identifier after you have investigated that this is a real need and you can’t switch the NLB’s to HLB’s. Also make sure that this is what you have and not duplicate Agent GUID’s!! With other words: BE CAREFUL!

Below some references…

Understanding how the Agent GUID is used by the ePolicy Orchestrator server [8078252]
https://knowledge.mcafee.com/SupportSite/dynamickc.do?sliceId=SAL_Public&command=show&forward=nonthreadedKC&externalId=8078252

Unable to see both nodes of a cluster in the ePO directory because of duplicate MAC address issue [KB45372]
https://knowledge.mcafee.com/article/914/KB45372_f.SAL_Public.html

ePO agents do not appear in the directory after imaged computers are deployed
https://knowledge.mcafee.com/article/106/KB40636_f.SAL_Public.html

Posted in McAfee | Leave a Comment »

Jeff Dunham

Posted by bartvdw on 2727/0101/2008

http://www.jeffdunham.com/

You can find also some videos on YouTube from this guy, he’s really amazing!

Posted in Fun | Leave a Comment »

POP3 Connector: How to troubleshoot

Posted by bartvdw on 2727/0101/2008

How to troubleshoot the POP3 Connector in Windows Small Business Server 2003
http://support.microsoft.com/kb/885685

Posted in Exchange, SBS | Leave a Comment »

POP3 Connector: Important fixes

Posted by bartvdw on 2727/0101/2008

Here are some very important hotfixes for POP3 Connector in SBS. I have seen the issues several times.

Many unexpected outbound e-mail messages appear in the SMTP queue in Small Business Server 2003
http://support.microsoft.com/kb/835734

Download link: http://www.microsoft.com/downloads/details.aspx?familyid=7B1FF109-092E-4418-AA37-A53AF7B8F6FC&displaylang=en

Scheduled POP3 connector e-mail message downloads may not occur on your Windows Small Business Server 2003-based computer
http://support.microsoft.com/kb/833992

Download link: http://www.microsoft.com/downloads/details.aspx?familyid=206e4e32-1e37-4836-b4f7-8d6a543a7c7f&displaylang=en

Posted in Exchange, SBS | Leave a Comment »

Allocated memory issue: sqlservr.exe

Posted by bartvdw on 2626/0101/2008

Recently I found on a SBS 2003 box a memory issue. After a quick look in my Task Manager I found that the process was called sqlservr.exe

Next step was finding the service linked to the process. “tlist.exe -s” (included in Debugging Tools for Windows) gave me the information needed: MSSQL$SBSMONITORING

What to do about that? Well after searching a little bit, I found this solution:

  • Open cmd
  • osql -E -S YOURSERVERNAME\sbsmonitoring [hit enter]
  • sp_configure ‘show advanced options’,1 [hit enter]
  • reconfigure with override [hit enter]
  • go [hit enter]
  • sp_configure ‘max server memory’, 70 [hit enter] (based on the information I found, this is OK)
  • reconfigure with override [hit enter]
  • go [hit enter]

Note: mind the quotes used! I have problems with publishing them correctly, so if you receive an error pointing into that direction, correct them manually in your syntax.

Cool link that helped me a lot:
http://msmvps.com/blogs/bradley/archive/2005/02/04/34984.aspx

 

Update

Troubleshooting High Memory Usage by a MSDE Instance.
http://blogs.technet.com/asksbs/archive/2008/07/05/troubleshooting-high-memory-usage-by-a-msde-instance.aspx

Adjusting SQL embedded instances
http://msmvps.com/blogs/bradley/archive/2007/12/25/adjusting-sql-embedded-instances.aspx

Thanks again Susan for the great post on this subject !!!

Posted in SBS, SQL | 1 Comment »

Powercfg.exe utility

Posted by bartvdw on 2626/0101/2008

Today I discovered a very nice utility: powercfg.exe

Reason was that I received the question for force a specific power scheme on clients, namely monitor should go to standby after 30 minutes. Client OS is Windows XP, no GPO settings found to accomplish the task. Then I found the powercfg.exe utility. Adding this is a simple script with some standard schemes (.pow files) solved my issue forever!

Works perfectly on Windows XP & Windows Server 2003…

Edit: GPP extends power settings if you’re capable using them…

How to use Powercfg.exe in Windows Server 2003
http://support.microsoft.com/kb/324347

POWERCFG [/LIST | /QUERY [name] | /CREATE name | /DELETE name |
       /SETACTIVE name | /CHANGE name settings |
       /HIBERNATE {ON|OFF} | /EXPORT name [/FILE filename] |
       /IMPORT name [/FILE filename] | /GLOBALPOWERFLAG {ON|OFF} /OPTION flag |
       /BATTERYALARM {LOW|CRITICAL} [settings] |
       /DEVICEQUERY queryflags | /DEVICEENABLEWAKE devicename |
       /DEVICEDISABLEWAKE devicename | /?]

Description:
    This command line tool enables an administrator to control
    the power settings on a system.

Parameter List:
    /LIST, /L       Lists the names of existing power schemes.
    /QUERY, /Q      Displays the configuration of the specified power scheme.
                    If no name is specified, the configuration of the currently
                    active power scheme is displayed.
    /CREATE, /C     Creates a power scheme with the specified name.  The new
                    scheme is created with the properties of the currently
                    active scheme.
    /DELETE, /D     Deletes the power scheme with the specified name.
    /SETACTIVE, /S  Makes the power scheme with the specified name active.
    /CHANGE, /X     Changes settings of the specified power scheme. Additional
                    switches specify the changes as follows:
                        /monitor-timeout-ac <minutes>
                        /monitor-timeout-dc <minutes>
                        /disk-timeout-ac <minutes>
                        /disk-timeout-dc <minutes>
                        /standby-timeout-ac <minutes>
                        /standby-timeout-dc <minutes>
                        /hibernate-timeout-ac <minutes>
                        /hibernate-timeout-dc <minutes>
                        /processor-throttle-ac <throttle>
                        /processor-throttle-dc <throttle>
                    AC settings are used when the system is on AC power.
                    DC settings are used when the system is on battery power.
                    Setting a timeout to zero will disable the corresponding
                    timeout feature.  Supported throttle settings are NONE
                    CONSTANT, DEGRADE, and ADAPTIVE.
    /EXPORT, /E     Exports the power scheme with the specified name to a
                    file.  If no filename is specified, the default is
                    SCHEME.POW.  This additional parameter is supported:
                        /FILE <filename>
    /IMPORT, /I     Imports the power scheme from a file under the specified
                    name.  If no filename is specified, the default is
                    SCHEME.POW.  If a scheme with that name already exists, it
                    is replaced with the new one.  This additional parameter
                    is supported:
                        /FILE <filename>
    /HIBERNATE, /H {ON|OFF}  Enables/Disables the hibernate feature.  Hibernate
                    timeout is not supported on all systems.
    /NUMERICAL, /N  Allows the power scheme to be operated upon to be specified
                    using a numerical identifier.  When using this switch, in
                    place of the name of the power scheme on the command line,
                    specify its numerical identifier.  This switch may be used
                    in combination with the /QUERY, /DELETE, /SETACTIVE,
                    /CHANGE, /EXPORT, and /IMPORT commands.
    /GLOBALPOWERFLAG, /G {ON|OFF}  Turns one of the global power flags on/off.
                    Valid flags (to be used after "/OPTION ") are:
                         BATTERYICON:    Turns the battery meter icon in the
                                         system tray on/off.
                         MULTIBATTERY:   Turns on/off multiple battery display
                                         in system Power Meter.
                         RESUMEPASSWORD: Prompt for password on resuming the
                                         system.
                         WAKEONRING:     Turn on/off wake on ring support.
                         VIDEODIM:       Turn on/off support for dimming video
                                         display on battery power.
    /AVAILABLESLEEPSTATES, /A  Reports the sleep states available on the
                    system.  Attempts to report reasons why sleep states are
                    unavailable.
    /BATTERYALARM, /B {LOW|CRITICAL}  Configures the battery alarm.  The
                    following switches can be specified:
                        /activate <on|off>
                            Enables or disables the alarm.
                        /level <percentage (0 – 100)>
                            The alarm will be activated when the power level
                            reaches this percentage.
                        /text <on|off>
                            Turns the text notification on or off.
                        /sound <on|off>
                            Turns the audible notification on or off.
                        /action <none|shutdown|hibernate|standby>
                            Specifies the action to take when this alarm goes
                            off.  Not all actions are always available.
                        /forceaction <on|off>
                            Force stand by or shutdown even if a program stops
                            responding.
                        /program <on|off>
                            Specifies a program to run.  schtasks.exe /change
                           may be used to configure the program.
    /DEVICEQUERY <queryflags> will return a list of devices that meet the
                    criteria specified in <queryflags>.  Possible values
                    for <queryflags> are:
                    wake_from_S1_supported – return all devices that support
                             waking the system from a light sleep state.
                    wake_from_S2_supported – return all devices that support
                             waking the system from a deeper sleep state.
                    wake_from_S3_supported – return all devices that support
                             waking from the deepest sleep state.
                    wake_from_any – return all devices that support waking
                             from any sleep state.
                    S1_supported – list devices supporting light sleep states.
                    S2_supported – list devices supporting deeper sleep.
                    S3_supported – list devices supporting deepest sleep.
                    S4_supported – list devices supporting system hibernation.
                    wake_programmable – list devices that are user-configurable
                             to wake the system from a sleep state.
                    wake_armed – list devices that are currently configured to
                             wake the system from any sleep state.
                    all_devices – return all devices present in the system.
                    all_devices_verbose – return verbose list of devices.
    /DEVICEENABLEWAKE <devicename> enable the device to wake the system from a
                    sleep state. <devicename> is a device retrieved using
                    the ‘/DEVICEQUERY wake_programmable’ parameter.
    /DEVICEDISABLEWAKE <devicename> disable the device from waking the system
                    from a sleep state. <devicename> is a device retrieved
                    using the ‘/DEVICEQUERY wake_armed’ parameter.
    /HELP, /?       Displays information on command-line parameters.

Examples:
    POWERCFG /LIST
    POWERCFG /QUERY scheme
    POWERCFG /QUERY
    POWERCFG /CREATE scheme
    POWERCFG /DELETE scheme
    POWERCFG /SETACTIVE scheme
    POWERCFG /CHANGE scheme /monitor-timeout-dc 15
    POWERCFG /CHANGE scheme /monitor-timeout-dc 0
    POWERCFG /HIBERNATE on
    POWERCFG /EXPORT scheme /file file
    POWERCFG /QUERY number /NUMERICAL
    POWERCFG /GLOBALPOWERFLAG on /OPTION BATTERYICON
    POWERCFG /AVAILABLESLEEPSTATES
    POWERCFG /BATTERYALARM low
    POWERCFG /BATTERYALARM critical /ACTIVATE on /LEVEL 6 /ACTION hibernate
    POWERCFG /DEVICEQUERY wake_armed
    POWERCFG /DEVICEENABLEWAKE "Microsoft USB IntelliMouse Explorer"

Posted in Windows | 16 Comments »