SharePoint web services

It's interesting how SharePoint Web Services works. Will add here useful links and my own comments based on my research.
Useful links:
Getting Started With SharePoint Web Services

The SharePoint web services are implemented in ASP.NET Web Services (ASMX), and you will find the physical files for most of these web services in the "Microsoft Shared" directory under "web server extensions\12\ISAPI" typically located at "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI". The admin web service for the Central Administration tool is located in the ADMISAPI folder for which the central administration console contains a virtual directory named "_vti_adm". When a SharePoint site is created it will contain a virtual directory named "_vti_bin" that points to this location. IIS does not contain any application or virtual directories for subwebs, they do however contain mapping to the _vti_bin virtual directory through SharePoint metadata and HttpModules.

Talk to SharePoint Through Its Web Services

List of SharePoint services includes the following:

WSS Web Services	Web Reference
Administration Service	http://server/_vti_adm/admin.asmx
Alerts Service	http://server/_vti_bin/alerts.asmx
Document Workspace Service	http://server/_vti_bin/dws.asmx
Forms Service	http://server/_vti_bin/forms.asmx
Imaging Service	http://server/_vti_bin/imaging.asmx
List Data Retrieval Service	http://server/_vti_bin/dspsts.asmx
Lists Service	http://server/_vti_bin/lists.asmx
Meetings Service	http://server/_vti_bin/meetings.asmx
Permissions Service	http://server/_vti_bin/permissions.asmx
Site Data Service	http://server/_vti_bin/sitedata.asmx
Site Service	http://server/_vti_bin/sites.asmx
Users and Groups Service	http://server/_vti_bin/usergroup.asmx
Versions Service	http://server/_vti_bin/versions.asmx
Views Service	http://server/_vti_bin/views.asmx
Web Part Pages Service	http://server/_vti_bin/webpartpages.asmx
Webs Service	http://server/_vti_bin/webs.asmx

MSDN

UAC prevents execution of custom actions during msi installation

In the previous post there was a link to the Robert Flaming's blog where he describes how MSI works with UAC. But I have some additional comments and want write them here:

In the following post Robert describes how permissions change under UAC:

• the Violet region runs as Standard User
• the Orange region runs as Standard User
• the Teal region
  • Standard Actions run as with the needed permissions
  • Custom Actions run as Standard User unless the NoImpersonate bit is flipped.

But what does the NoImpersonate bit means? There are different explanations in different articles. Based on my testing I've found out the following:

When you set Impersonate="no" in WIX for you custom action, it means that the custom action will be executed under the Local System account. And it is fine if you need to do changes with your local system. But if your custom action accesses a remote server it fails.

So, the only way that I've found is to prohibit the msi execution under unprivileged user. You should set the MSIUSEREALADMINDETECTION property to 1 and add a Launch Condition for Privileged that gives an error message about running via an elevated command prompt and then quits the installation.

<Property Id="MSIUSEREALADMINDETECTION" Value="1" />




<Condition Message="The installation should be running with full administrative account. Please run an administrative command prompt and launch installation using msiexec.">

Privileged

</Condition>

MSI and UAC

The very useful blog

Content is the following:

1. Introduce...
   1. ...the UAC in MSI Notes series
   2. ...my view of the root problem
   3. ...the conflicting per-user definition
   4. ...it'll be just like Managed Installs
   5. ...the jagged edge to user
   6. ...my relief providing framework
2. Architecture Insights
   1. The "Saw Tooth" Diagram
   2. Credential Prompt and Permissions
3. Common Package Mistakes
   1. The AdminUser Mistake
   2. Modify System with InstallUISequence Custom Action
   3. Modify System with InstallExecuteSequence Custom Action Outside of Script
   4. The NoImpersonate Bit Mistake
4. More Architectural Insights
   1. My "Four Square" Diagram
   2. Challenges for a Beautiful Custom Action
   3. O Whitepaper, Where Art Thou?
   4. Read the Friendly Manual
5. Conversations with Customers
   1. Should I write my installer as a Standard User install? If yes, how?
   2. When General Custom Action Mitigation Fails
   3. How do I get the shield on the advertised shortcut?
   4. How do I troubleshoot UAC in MSI via the log?
   5. Do I need to consider "this" when I'm designing for UAC in MSI? Generally, no.
   6. Is "this" intentional? If so, why?
   7. How to Build Packages that work for both Standard User and Per-Machine?
   8. Easier for my current custom installer to support UAC than switch to MSI?
   9. How do I get one credential dialog for a multiple package install?
   10. What are the Hurdles in Windows Vista Logo compliance related to UAC and MSI?