Ivan Lučić - my blog

Windows Installation very slow –> simple solution

Ivan Lučić — Tue, 15 Sep 2009 19:22:45 GMT

Platforms:

Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2

Problem:

Extremely slow Windows installation on your brand new machine.

Cause:

If you have no floppy drive installed in your computer, check if it’s still enabled. Some BIOS versions have problems with detecting a non-existing floppy drive and report it to the OS as present.

However the Windows XP setup seems not to be so sensitive.

Solution:

Enter the BIOS and set the floppy drive to “none”. Don’t ask.

Skype 3.0 for Windows Mobile finally released

Ivan Lučić — Fri, 03 Jul 2009 21:37:20 GMT

Features:

Call phones and mobiles at low rate (worldwide)
Free Skype-to-Skype calls
Free instant messaging

New features:

Send files Skype-to-Skype
Send SMS at much lower rate

For the best call quality, Skype recommends you sign in to Skype from a WiFi connection. You can also sign in from a 3G (UMTS) connection, but check first if your provider is blocking VoIP connections.

Requirement: Phone with Windows Mobile 5, 6, 6.1 and probably 6.5

Current version: 3.0.0.256

Release date: June 29, 2009

Download: http://www.skype.com/download/skype/windowsmobile/

Deutsch (German): http://www.skype.com/intl/de/download/skype/windowsmobile/

DFS & Access-based enumeration (ABE)

Ivan Lučić — Tue, 16 Jun 2009 14:00:41 GMT

Platform: Windows Server 2008 Enterprise x64 English SP2

DFS Namespace type: Domain-based

In my current file-server environment I’m using the Access-based enumeration on all global file shares. ABE allows filtering folders visible to a user based on his NTFS access rights.

Additionally I’m using the Distributed File System (DFS), so I tried to join these both features.

Windows Server 2008 has the ABE feature already integrated. Everything you need to do is to activate it within the share’s properties (Server Manager –> Roles –> File Services –> Share and Storage Management –> your share –> properties):

On Windows Server 2003 you have to install the Windows Server 2003 Access-based Enumeration interface to be able to activate the ABE. After the installation you will find a new tab named “Access-based Enumeration” in your folder’s properties (if the folder is already shared):

(now first the wrong way to setup the DFS with ABE)

In my domain forest the fileservers are distributed in several sub domains. So I created a namespace in the root domain (on all root DC’s) to have one global entry point for all of the company file-data. The namespace is called “\\myrootdomain.local\DATA”. Inside of the namespace I created folder-links to several file-servers. In the next step I turned on the ABE for the DATA file share on every namespace-holder (DC). Additionally I configured the NTFS Security for all links on each node manually. First all links were visible for all users because of the inherited object security from the root drive. So I turned it off on each link separately, copied the permission entries, deleted the domain user entries and added the universal security groups (appropriate to the domain) for DFS with read only access to the links.

First tests were successful, but a few days later the links would lose the custom settings. The NTFS inherited security was enabled again – probably activated by the Windows Dfs Service. In some cases the ABE settings was changed as well.

…so I searched for the solution…and here is the right way:

First I checked the ABE support with DFS, and it’s really supported by the Windows Server 2008, but the namespace must be running in Windows Server 2008 mode. Slow-clickers (I’m not :)) would read it while creating the namespace:

Also you have to set this checkbox while creating the namespace for this feature to be supported. Otherwise the namespace would run in Windows 2000 Server mode, like here:

If you have already created the namespace you will have to recreate it. During the recreation you will possibly not be able to check the “2008 mode”, it could be grayed out. The reason for that is the requirement to have the Active Directory running in Windows Server 2008 domain functional level (not the whole forest). This against requires all DC’s in this domain (not forest) to run Windows Server 2008.

Again, the Windows Server 2008 domain functional level is only required in the domain where the namespace servers are located.

Raising the domain functional level to “Windows Server 2008”:

Check all DC’s running Windows Server 2008 and be sure that you are not planning to add a Windows 2000 or 2003 DC in the future to this domain.
Raise the domain functional level to “Windows Server 2008” (Active Directory Users and Computers –> right click on your domain –> Raise domain functional level…)
Wait for AD replication or replicate manually

Now restart the Windows Dfs Service on all Namespace nodes and you will be able to create and run the namespace in 2008 mode, like here:

Next: ABE and NTFS security configuration

Before you begin to configure these settings (ABE, NTFS) manually – please don’t do it on the conventional way (folder/share properties) – this way is not supported, the settings would not be replicated. Windows Server 2008 supports only the command-line administration of these features. The Administration within the GUI will not be supported until Windows Server 2008 R2.

The following steps must be done once only. The settings will be pushed to the other servers!

1. Enable the ABE (ABDE - Access Based Directory Enumeration) for the namespace using the dfsutil.exe:

dfsutil.exe Property ABDE Enable \\yourdomain.local\NamespaceName

Check the state with the following command:

dfsutil.exe Property ABDE \\yourdomain.local\NamespaceName

2. Set the NTFS Security like the following:

Remove all security settings:

dfsutil.exe Property ACL Reset \\yourdomain.local\DATA\Link1

Disable object inheritance:

dfsutil.exe Property ACL Control \\yourdomain.local\DATA\Link1 Protect

Set access rights for the Domain Admins (Full) and the DFS security group (more than read-only is not necessary here):

dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link1 "yourdomain.local\Domain Admins":F
dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link1 yourdomain.local\dfs-group_company1:R

And here the sample for the other links:

dfsutil.exe Property ACL Reset \\yourdomain.local\DATA\Link2
dfsutil.exe Property ACL Control \\yourdomain.local\DATA\Link2 Protect
dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link2 "yourdomain.local\Domain Admins":F
dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link2 subdom1.yourdomain.local\dfs-group_company2:R

dfsutil.exe Property ACL Reset \\yourdomain.local\DATA\Link3
dfsutil.exe Property ACL Control \\yourdomain.local\DATA\Link3 Protect
dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link3 "yourdomain.local\Domain Admins":F
dfsutil.exe Property ACL Grant \\yourdomain.local\DATA\Link3 subdom2.yourdomain.local\dfs-group_company3:R

You can verify the results within the windows folder properties security tab but always set the NTFS security with the dfsutil.exe.

The used security groups should also be used to set the root-folder security on the linked file-servers shares. Additionally check if the ABE is enabled there also (How-to? See top of the blog).

In most cases the share on your file-server holds folders named according to company’s departments. Best practice is to create a universal security group for every folder in the root of this share and set the permissions on them. Better you create one group for write- and another one for read-access and set the NTFS settings for these groups, one with modify and the other one with read permissions. Then make all of these folder access groups as member of the company’s DFS security group to have automatically access to the share and the DFS.

Now, users (better whole department (global) security groups) have only to be a member of the selected folder security group’s (R or RW) to have access through all DFS levels. The NTFS permissions must be never touched again - the administration can completely be done via the Active Directory.

Finally map a network drive to “\\yourdomain.local\DATA” - one for the whole domain forest! ;)

DFS Namespace Management: Error - The server you specified already hosts a namespace with this name

Ivan Lučić — Mon, 15 Jun 2009 10:30:17 GMT

Platform: Windows Server 2008 Enterprise x64 English SP2

Namespace type: Domain-based

In my last post about the DFS (DFS Namespace Management: The namespace cannot be queried. The RPC server is unavailable.) I have explained how to delete a corrupted namespace from the Active Directory. Anyway the recreation of the same namespace would not work on hosts which have already hosted this namespace.

Thereby you would probably get the following error: “The server you specified already hosts a namespace with this name. Please select another namespace name or another server to host the namespace.”

Additionally to the namespace deletion in the domain follow the following steps to manually remove the remaining namespace parts on your DFS host:

Run “dfsutil.exe diag viewdfsdirs c: RemoveReparse” to remove all DFS folders from this host (it’s not possible to remove only a part of them, so be sure). If your DFSRoot was not placed on the c: drive, replace the parameter “c:” with the proper drive letter.
Delete the following three registry keys/values:
1. HKLM\SOFTWARE\Microsoft\Dfs\Roots\Domain\YourOldNamespace
2. HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares\YourOldNamespaceShare
3. HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares\Security\YourOldNamespaceShare
Reboot your Windows Server. The restart of the both services Dfs (DFS Namespace) and LanmanServer (Server) is not sufficient enough.
Delete the namespace folder in the DFSRoot.

bing vs. Google vs. Yahoo! (very cool)

Ivan Lučić — Mon, 08 Jun 2009 14:40:40 GMT

So far there was no simple way to compare search results of the big three.

Blind Search allows you to send your search query to all of them at the same time. The result will be returned in three (random ordered and neutral formatted) columns with no search engine assignment. As next you compare the results and vote for the “column” with the best result to get the assignment. Exciting & very cool!

Link: http://blindsearch.fejus.com/

Result of my three (not really representative) searches:

2 –> bing (Wow!)

1 –> Yahoo!

0 –> Google

Please comment your results! ;)

ps: You will wonder if the results are not always the same like the search results on your search engine directly. Cause is the fixed US localization of Blind Search. Your client localization is not being passed through.

DFS Namespace Management: The namespace cannot be queried. The RPC server is unavailable.

Ivan Lučić — Mon, 08 Jun 2009 12:57:09 GMT

Platform: Windows Server 2008 Enterprise x64 English SP2

Namespace type: Domain-based

Problem:

You are trying to manage or delete a domain-based DFS namespace once hosted on an old (or crashed) machine. In doing so you get the following error: “The namespace cannot be queried. The RPC server is unavailable.”

Error when trying to delete the namespace (right-click before connecting):

Error when trying to connect:

Resolution:

Delete the namespace using ADSI Edit and dfsutil.exe.

Steps:

DFS Server: Remove the affected namespace from the DFS Management display.
DC: Use ADSI Edit to connect to the “Default naming context” of the affected domain, browse to CN=System, CN=Dfs-Configuration and delete the namespace entry.
DC: Wait for AD replication or replicate the changes manually.
DFS Server: Use dfsutil to flush all DFS caches. To do this start cmd.exe as Administrator and run the following three commands:
- dfsutil cache domain flush
- dfsutil cache referral flush
- dfsutil cache provider flush

Now the namespace should not be listed when you run the “Add Namespaces to Display…” action and you should be able to create a new namespace with the old name.

Remote WMI: "Error: Access Denied" / "Win32: Access is denied", RSoP: "Error: Could not connect"

Ivan Lučić — Tue, 18 Nov 2008 15:01:00 GMT

PROBLEM:

You are using Group Policy Inventory (GPInventory.exe) to gather some information about the machines in your network (mostly Windows XP).

Thereby you get some really incredible results:

"Error: Access Denied" on WMI (Windows Management Instrumentation) queries:

"Error: Could not connect" on RSoP (Resultant Set of Policy) queries:

With the above clients (that you cannot establish connection with), the remote connection over WMI Control should also fail with the following error: "Win32: Access is denied" [german] "Win32: Zugriff verweigert" [/german]:

[german]

[/german]

If you want to test it, you can find that control here:

Control Panel -> Administrative Tools -> Computer Management -> Connect to another computer... -> choose your client & click OK -> Services and Applications -> WMI Control -> Properties

[german] Systemsteuerung -> Verwaltung -> Computerverwaltung -> Verbindung mit anderem Computer herstellen... -> Client wählen & OK klicken -> Dienste und Anwendungen -> WMI-Steuerung -> Eigenschaften [/german]

Whatta...!?! What happens here? Everything seems to be fine:

you are logged in as a domain administrator
all the clients are domain members and you are admin on these machines as well
there is no firewall active between the machines in your network (XP firewall is off)
there are no errors in the event log and all the services are running properly
WMI Control connect locally (on the clients) works anyway

CAUSE:

DCOM (Distributed COM) seems to be deactivated on your client(s).

RESOLUTION:

Activate it, what else ;)

But beware of worms and viruses, many of them are based on this technology. Activate this setting only in internal (secure) networks, behind the firewall and your AntiVirus wall.

Activate the firewall on mobile clients, especially in the Standard Profile Policy. If the firewall ist activated in the Domain Profile, you can add management exceptions like the following:

How to configure Windows Firewall in Windows XP Service Pack 2 to allow remote administration tools that use WMI, RPC, or DCOM

[german] Konfigurieren der Windows Firewall in Windows XP Service Pack 2, um Remoteverwaltungstools zuzulassen, die WMI, RPC oder DCOM verwenden [/german]

Steps for manual DCOM activation:

Control Panel -> Administrative Tools -> Component Services (short: run dcomcnfg.exe)
Component Services -> Computers -> My Computer -> Properties -> Default Properties
Check "Enable Distributed COM on this computer"
OK
Restart the machine

[german]

Schritte für manuelle Aktivierung des DCOM:

Systemsteuerung -> Verwaltung -> Komponentendienste (kurz: dcomcnfg.exe ausführen)
Komponentendienste -> Computer -> Arbeitsplatz -> Eigenschaften -> Standardeigenschaften
Häkchen bei "DCOM (Distributed COM) auf diesem Computer aktivieren" setzen
OK
Maschine neu starten

[/german]

On the Windows Vista and the PDC Beta of Windows 7, the Component Services are not located in the Administrative Tools anymore.

To start them anyway, do one of the following (this works in XP/2003 as well):

Start the Management Console (mmc.exe) and add the Component Services Snap-in
simply run dcomcnfg.exe
or run comexp.msc

I haven't searched for group policy setting to activate DCOM, but you are welcome to publish it within your comment ;)

PDC: Windows 7 Software Logo Program Requirements

Ivan Lučić — Mon, 27 Oct 2008 14:24:00 GMT

Microsoft just published the preview version of the Windows Seven Software Logo Program for Client Technical Requirements document. All interested developers should take a look at this.

Finally to get the Logo all software must support x64 versions of Windows!

At first it's necessary to match these criteria:

Include business and technical owners for all submissions
Opt in to receive communications from Microsoft about their products
Include a copy and license of the software for compatibility testing purposes
Along with Microsoft agree to a 30-90 day resolution policy for all issues identified in market with logo'd products
Ensure the application adheres to all policies and passes all requirements in this document

Three additional policies:

Comply with Anti-spyware Coalition Guidelines
Do not modify Windows Resource Protection (WRP) protected resources
Ensure ongoing quality - in short, fix crash reports over time

And finally 10 technical requirements:

Install and uninstall cleanly
Install to the correct folders by default
Support x64 versions of Windows
Follow User Account Control (UAC) Guidelines
Do not load Services and Drivers in Safe Mode
Digitally Sign Files
Do not prevent an installation or application from launching because of OS version checking
Prevent unnecessary reboots
Support multiuser sessions
Minimize application failures

Vista SP2 Beta1 - Download over WU

Ivan Lučić — Fri, 24 Oct 2008 14:49:00 GMT

WARNING: This is a Beta1 version of the Vista SP2, only for testing purposes!

1. create a batch file with the following content:

@echo off

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSp2 /f > NUL 2>&1
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSP2 /f > NUL 2>&1

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSp2 /v Beta1 /t REG_SZ /d C21A5C64-2530-CC19-042F-9ABDB4ED27F9 /f
IF NOT %errorlevel% == 0 ( goto ERROR)

:SUCCESS
@echo.
echo ================================================== =========
echo Windows Vista SP2 registry key has been set successfully.
echo Please check for updates in Windows Update.
echo Ejoy with SP2. Dev...
echo ================================================== =========
@echo.
goto END

:ERROR
@echo.
echo ================================================== =========
echo FAILED to set Windows Vista SP2 registry keys.
echo Please run this script by right clicking and selecting
echo "Run as Administrator".
echo ================================================== =========
@echo.
goto END

:END
pause

2. run the file as administrator

3. run windows update

4. good luck ;)

Sony Ericsson XPERIA X1 - the maybe best Windows Mobile phone?? ..it will be released this month!! :)

Ivan Lučić — Wed, 10 Sep 2008 12:55:00 GMT

The shipping will be started in the UK, Germany and Sweden (30th September). In other countries by the end of the year.

Highlights:

3" WVGA-Touch-TFT (800x480, 65536 colors)
QWERTY/QWERTZ slide keyboard
3.2 MP cam with flash, video (VGA, 30 fps)
second cam for videocall at the front
16.7 mm "thin"
Windows Mobile 6.1 Professional
Quad-band
EDGE/HSDPA/HSUPA
A-GPS
WLAN b/g
Bluetooth v2.0 (A2DP) - no IR
RDS FM radio
Vibration
no accelerometer
528 MHz CPU
384 MB RAM
512 MB internal storage (max. 400 available)
microSD slot (HC compatible)
miniUSB 2.0
3.5 mm audio jack
Batt: Li-Po 1500 mAh
Stand-by: up to 35 days!!
Talk time: up to 10h
Colors: Solid Black or Steel Silver

News source: http://www.gsmarena.com/sony_ericsson_xperia_x1_coming_in_only_three_weeks_time-news-587.php

Product site: http://www.sonyericsson.com/x1

EU price comparison without contract: http://geizhals.at/eu/a313867.html

Finally - The first SQL Server 2008 release candidate - download for everyone

Ivan Lučić — Wed, 11 Jun 2008 19:44:00 GMT

Yesterday Microsoft published the SQL Server 2008 as Release Candidate 0

Platforms: x86, x64, IA64

Available languages: English, French, German, Italian, Japanese, Korean, Spanish, Chinese - Simplified and Traditional

Download link: http://www.microsoft.com/downloads/details.aspx?FamilyID=35f53843-03f7-4ed5-8142-24a4c024ca05&DisplayLang=en

RC0 readme: http://www.microsoft.com/downloads/details.aspx?FamilyID=298c5443-cc7c-4c22-8d73-fb70c96b5b04&DisplayLang=en

Site with download links for TechNet and MSDN users: http://msdn.microsoft.com/subscriptions/cc526022.aspx

Vista SP1 available for download (release)

Ivan Lučić — Fri, 15 Feb 2008 09:27:00 GMT

WOW! ;)

As MSDN/Technet subscriber we are finally able to download the release of the Vista SP1!

Available are packages for 32 and 64-bit Systems in English, French, German, Japanese and Spanish.

File details:

Title: Windows Vista Service Pack 1 (x86, x64) - DVD (English, French, German, Japanese, Spanish)
Filename: de_en_es_fr_ja_windows_vista_service_pack_1_x86_x64_dvd_X14-38128.iso
Size: 1.13 GB

Title: Windows Vista Service Pack 1 (x86) - EXE (English, French, German, Japanese, Spanish)
Filename: de_en_es_fr_ja_windows_vista_service_pack_1_x86_72327.exe
434.5 MB

Title: Windows Vista Service Pack 1 (x64) - EXE (English, French, German, Japanese, Spanish)
Filename: de_en_es_fr_ja_windows_vista_service_pack_1_x64_72328.exe
Size: 726.5 MB

Download it here directly under "Top Subscriber Downloads":

http://msdn2.microsoft.com/en-us/subscriptions/default.aspx

The integrated full install of Vista with SP1 will be available to the end of the month.

Sources:

http://blogs.technet.com/technetplussubscriptions/archive/2008/02/14/technet-plus-vista-sp1-available-for-download.aspx

http://windowsvistablog.com/blogs/windowsvista/archive/2008/02/11/windows-vista-sp1-availability-for-technical-customers.aspx

Changes made on windows service properties, by editing the registry, would not take an effect until system is restarted

Ivan Lučić — Wed, 24 Oct 2007 07:26:00 GMT

Few days ago I tried to change some windows service properties by directly editing the registry keys. Amongst others I tried to allow some service to interact with the desktop on my Windows XP machine.
Under “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyService” I added 256 (Hex 100) to the “Type” value. Then I started the service and nothing happened. The reg key was still there and the check-box under the Service properties was checked, but the service was still not interacting with my desktop, hmm.
I unchecked the box and reapply the same settings again, restarted the service and then it worked.
It seems that this registry keys are not watched, probably they will be read only once at the start of system / service-manager.
I have not tried it yet but I think under Windows 2000 and Server 2003 you can expect the same behavior.
(I heard that Vista doesn’t make your life any easier at all with service-desktop-interacting due to security issues and interacting might not even work when allowed. I will cover this topic at the next time, till then enjoy XP.)
The question is: “What is behind this GUI “Apply” button except the setting of the reg-keys?”
Possibly something like: “Hey dear WinAPI, look at this key, I have just changed it” or one of my methods below.
I don’t know what is behind this button, but here I will show you four methods of how you can change this setting and point out their pros and cons.
Ahead I'm sorry because of shitty formatted C# Code, therefore I attached the code files for download.

Note that allowing your service to interact with the desktop can be dangerous.
Microsoft’s Caution:
In most cases, it is recommended that you not change the Allow service to interact with desktop setting. If you allow the service to interact with the desktop, any information that the service displays on the desktop will also be displayed on an interactive user's desktop. A malicious user could then take control of the service or attack it from the interactive desktop.

Method 1: Using the mouse ;)
-Run: services.msc
-Go to properties of your service, tab: “Log On”
-Choose “Local System account” (Lokales Systemkonto) and check the box “Allow service to interact with desktop” (Datenaustausch zwischen Dienst und Desktop zulassen)
-Apply it and restart your service

Pros:
-click, click... fast for one machine

Cons:
-nothing for networks

Method 2: Change the registry key by using the registry editor, some script or from your code.
Pros:
-simple
-easy to set with several scripting technologies

Cons:
-machine restart required

C# example:

using Microsoft.Win32;

namespace AllowServiceToInteractWithDesktop

{

partial class AllowServiceToInteractWithDesktop

{

public static void OverReg(string s_ServiceName)

{

RegistryKey ckey = Registry.LocalMachine.CreateSubKey(

@"SYSTEM\CurrentControlSet\Services\"

+ s_ServiceName);

if (ckey != null)

if (ckey.GetValue("Type") != null)

ckey.SetValue("Type",((int)ckey.GetValue("Type") | 256));

}

Method 3: Using the WMI
Pros:
-simple
-works with remote machines

Cons:
-x

C# example:

using System.Management;

namespace AllowServiceToInteractWithDesktop

{

partial class AllowServiceToInteractWithDesktop

{

public static void OverWMI(string s_ServiceName)

{

ManagementObject wmiService =

new ManagementObject(

"Win32_Service.Name='" + s_ServiceName + "'");

ManagementBaseObject parameter =

wmiService.GetMethodParameters("Change");

parameter["DesktopInteract"] = true;

wmiService.InvokeMethod("Change", parameter, null);

}

Method 4: Using the Windows API
Pros:
-Cool hardcore solution
-faster than other methods but not really important in this case

Cons:
-very complex, except you copy my method ;)

C# example:

using System;

using System.Runtime.InteropServices;

namespace AllowServiceToInteractWithDesktop

{

partial class AllowServiceToInteractWithDesktop

{

[Flags]

enum ACCESS_MASK : uint

{

DELETE = 0x00010000,

READ_CONTROL = 0x00020000,

WRITE_DAC = 0x00040000,

WRITE_OWNER = 0x00080000,

SYNCHRONIZE = 0x00100000,

STANDARD_RIGHTS_REQUIRED = 0x000f0000,

STANDARD_RIGHTS_READ = 0x00020000,

STANDARD_RIGHTS_WRITE = 0x00020000,

STANDARD_RIGHTS_EXECUTE = 0x00020000,

STANDARD_RIGHTS_ALL = 0x001f0000,

SPECIFIC_RIGHTS_ALL = 0x0000ffff,

ACCESS_SYSTEM_SECURITY = 0x01000000,

MAXIMUM_ALLOWED = 0x02000000,

GENERIC_READ = 0x80000000,

GENERIC_WRITE = 0x40000000,

GENERIC_EXECUTE = 0x20000000,

GENERIC_ALL = 0x10000000,

DESKTOP_READOBJECTS = 0x00000001,

DESKTOP_CREATEWINDOW = 0x00000002,

DESKTOP_CREATEMENU = 0x00000004,

DESKTOP_HOOKCONTROL = 0x00000008,

DESKTOP_JOURNALRECORD = 0x00000010,

DESKTOP_JOURNALPLAYBACK = 0x00000020,

DESKTOP_ENUMERATE = 0x00000040,

DESKTOP_WRITEOBJECTS = 0x00000080,

DESKTOP_SWITCHDESKTOP = 0x00000100,

WINSTA_ENUMDESKTOPS = 0x00000001,

WINSTA_READATTRIBUTES = 0x00000002,

WINSTA_ACCESSCLIPBOARD = 0x00000004,

WINSTA_CREATEDESKTOP = 0x00000008,

WINSTA_WRITEATTRIBUTES = 0x00000010,

WINSTA_ACCESSGLOBALATOMS = 0x00000020,

WINSTA_EXITWINDOWS = 0x00000040,

WINSTA_ENUMERATE = 0x00000100,

WINSTA_READSCREEN = 0x00000200,

WINSTA_ALL_ACCESS = 0x0000037f

}

[Flags]

private enum SCM_ACCESS : uint

{

SC_MANAGER_CONNECT = 0x00001,

SC_MANAGER_CREATE_SERVICE = 0x00002,

SC_MANAGER_ENUMERATE_SERVICE = 0x00004,

SC_MANAGER_LOCK = 0x00008,

SC_MANAGER_QUERY_LOCK_STATUS = 0x00010,

SC_MANAGER_MODIFY_BOOT_CONFIG = 0x00020,

SC_MANAGER_ALL_ACCESS = ACCESS_MASK.STANDARD_RIGHTS_REQUIRED |

SC_MANAGER_CONNECT |

SC_MANAGER_CREATE_SERVICE |

SC_MANAGER_ENUMERATE_SERVICE |

SC_MANAGER_LOCK |

SC_MANAGER_QUERY_LOCK_STATUS |

SC_MANAGER_MODIFY_BOOT_CONFIG,

GENERIC_READ = ACCESS_MASK.STANDARD_RIGHTS_READ |

SC_MANAGER_ENUMERATE_SERVICE |

SC_MANAGER_QUERY_LOCK_STATUS,

GENERIC_WRITE = ACCESS_MASK.STANDARD_RIGHTS_WRITE |

SC_MANAGER_CREATE_SERVICE |

SC_MANAGER_MODIFY_BOOT_CONFIG,

GENERIC_EXECUTE = ACCESS_MASK.STANDARD_RIGHTS_EXECUTE |

SC_MANAGER_CONNECT | SC_MANAGER_LOCK,

GENERIC_ALL = SC_MANAGER_ALL_ACCESS

}

[Flags]

private enum SERVICE_ACCESS : uint

{

SERVICE_NO_CHANGE = 0xffffffff, //this value is found in winsvc.h

SERVICE_QUERY_CONFIG = 0x00000001,

SERVICE_CHANGE_CONFIG = 0x00000002,

SERVICE_QUERY_STATUS = 0x00000004,

SERVICE_ENUMERATE_DEPENDENTS = 0x00000008,

SERVICE_START = 0x00000010,

SERVICE_STOP = 0x00000020,

SERVICE_PAUSE_CONTINUE = 0x00000040,

SERVICE_INTERROGATE = 0x00000080,

SERVICE_USER_DEFINED_CONTROL = 0x00000100,

STANDARD_RIGHTS_REQUIRED = 0x000F0000,

SERVICE_ALL_ACCESS = STANDARD_RIGHTS_REQUIRED | SERVICE_QUERY_CONFIG |

SERVICE_CHANGE_CONFIG |

SERVICE_QUERY_STATUS |

SERVICE_ENUMERATE_DEPENDENTS |

SERVICE_START |

SERVICE_STOP |

SERVICE_PAUSE_CONTINUE |

SERVICE_INTERROGATE |

SERVICE_USER_DEFINED_CONTROL

}

[StructLayout(LayoutKind.Sequential)]

private class QUERY_SERVICE_CONFIG

{

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.U4)]

public UInt32 dwServiceType;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.U4)]

public UInt32 dwStartType;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.U4)]

public UInt32 dwErrorControl;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

public String lpBinaryPathName;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

public String lpLoadOrderGroup;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.U4)]

public UInt32 dwTagID;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)] public String lpDependencies;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

public String lpServiceStartName;

[MarshalAs(System.Runtime.InteropServices.UnmanagedType.LPWStr)]

public String lpDisplayName;

};

[DllImport("advapi32.dll", EntryPoint = "OpenSCManagerW", ExactSpelling = true, CharSet = CharSet.Unicode, SetLastError = true)]

private static extern IntPtr OpenSCManager(string machineName, string databaseName, uint dwAccess);

[DllImport("advapi32.dll", SetLastError = true, CharSet = CharSet.Auto)]

private static extern IntPtr OpenService(IntPtr hSCManager, string lpServiceName, uint dwDesiredAccess);

[DllImport("advapi32.dll", CharSet = CharSet.Unicode, SetLastError = true)]

private static extern Boolean QueryServiceConfig(IntPtr hService, IntPtr intPtrQueryConfig, UInt32 cbBufSize, out UInt32 pcbBytesNeeded);

[DllImport("advapi32.dll", CharSet = CharSet.Unicode, SetLastError = true)]

private static extern Boolean ChangeServiceConfig(IntPtr hService, UInt32 nServiceType, UInt32 nStartType, UInt32 nErrorControl, String lpBinaryPathName, String lpLoadOrderGroup, IntPtr lpdwTagId, String lpDependencies, String lpServiceStartName, String lpPassword, String lpDisplayName);

public static void OverWinAPI(string s_ServiceName)

{

IntPtr databaseHandle = OpenSCManager(null, null, (uint)SCM_ACCESS.SC_MANAGER_ALL_ACCESS);

IntPtr pServiceHandle = OpenService(databaseHandle, s_ServiceName, (uint)SERVICE_ACCESS.SERVICE_QUERY_CONFIG | (uint)SERVICE_ACCESS.SERVICE_CHANGE_CONFIG);

UInt32 dwBytesNeeded = 0;

// Allocate memory

IntPtr ptr = Marshal.AllocHGlobal(4096); QueryServiceConfig(pServiceHandle, ptr, 4096, out dwBytesNeeded);

QUERY_SERVICE_CONFIG qUERY_SERVICE_CONFIG = new QUERY_SERVICE_CONFIG();

Marshal.PtrToStructure(ptr, qUERY_SERVICE_CONFIG);

Marshal.FreeHGlobal(ptr);

ChangeServiceConfig(pServiceHandle, qUERY_SERVICE_CONFIG.dwServiceType | 256, (uint)SERVICE_ACCESS.SERVICE_NO_CHANGE, (uint)SERVICE_ACCESS.SERVICE_NO_CHANGE, null, null, IntPtr.Zero, null, null, null, null);

}

The Call

The calls to the three static methods looks like the following:

AllowServiceToInteractWithDesktop.OverReg("MyServiceName");

AllowServiceToInteractWithDesktop.OverWMI("MyServiceName");

AllowServiceToInteractWithDesktop.OverWinAPI("MyServiceName");

My hint: Use WMI, method 3!

Interesting talk (Video): Tandy Trower about Microsoft Robotics

Ivan Lučić — Fri, 07 Sep 2007 09:12:00 GMT

Here you can watch an interesting talk about the robots, the idea "a robot in every home" and the Microsoft Robotics. This video is very long, over an hour. The real (english) presentation begins at minute 2:30 ;)

VMware Workstation: Guests hardware not detected properly after upgrading to WS 6.0

Ivan Lučić — Fri, 07 Sep 2007 08:05:00 GMT

Yesterday I have upgraded my VMware Workstation from the version "5.5.3 build-34685" to "6.0.0 build-45731".
I started my machines and everything was looking fine but the machine’s Virtual Machine Hardware Compatibility was still "Workstation 5".
Then I installed the updated VMware Tools and upgraded the VM's Virtual Hardware to "Workstation 6" (Menu: “VM” -> “Upgrade or Change Version...” -> “Next” -> “Workstation 6” -> “Next” -> “Alter this virtual machine” -> “Next” -> “Finish” -> “Close”).
After I booted my Windows VM, all new hardware has been detected but the "Game Port for Creative" (Deutsch: "Gameport für Creative"). It appeared with a yellow exclamation mark in the Device Manager.
The device has following status:
"This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system."
Deutsch:
"Für dieses Gerät sind nicht genügend Ressourcen verfügbar. (Code 12) Wenn Sie dieses Gerät nutzen möchten, müssen Sie ein anderes Gerät mit Anschluss an den Computer deaktivieren."

Resolution:
Shut down your machine and downgrade the Virtual Machine Hardware Compatibility to "Workstation 5" again and then upgrade it to "Workstation 6" without starting the machine between these two changes!
All the glitches will be gone next time you start your machine.