Using WMI on Windows Server 2003

You might get "Invalid class" error when inquiring some information from Win32_SoftwareFeature, by calling WQL scripts like: "Select * From Win32_SoftwareFeature". As it turned out this feature is not installed by default on windows server 2003 and as result it gives you "Invalid class" when you call such scripts. It can be installed from add/remove programs - windows features:

Comments

Post a Comment

Popular posts from this blog

Client-side scripting for Taxonomy/Term Set Fields

    I haven’t found any way of how to attach to onchange event of term store fields for the edit/new forms, so I had to spend a couple of hours on reverse engineering of WebTaggingDialog.js and ScriptForWebTaggingUI.js and in piece of HTML which represents SharePoint FormField for Taxonomy field.      So, in HTML this field is bound as a set of spans, divs, hidden field and image to open WebTaggingDialog.aspx:   < SPAN id =ctl00_MyTaxonomyFieldID_ctl00_ctl00>     < INPUT id =ctl00_MyTaxonomyFieldID_ctl00_ctl01 class ="ms-taxonomy ms-taxonomy-height ms-long" value =MyTaxonomyFieldValue|f0d123d1-ac8c-4a18-bccb-65c9b5ea83af type =hidden>     < DIV id =ctl00_MyTaxonomyFieldID_ctl00_ctl02 class ="ms-taxonomy ms-taxonomy-height ms-long" InputFieldId ="ctl00_MyTaxonomyFieldID_ctl00_ctl01" SspId ="68e138c4-5729-4ddd-ab0d-95c688c6c8eb" GroupId ="00000000-0000-0000-0000-000000000000" TermSetId ="14
Read more

SharePoint delegate control is rendered twice

One of the situations where this might happen is - you deployed your control using one feature scope (Site for example) and than redeployed with another one (Web). So, you will see the control added twice to you pages. To fix this, simply: 1). switch to another feature scope (the one you no longer want to use), 2). deploy the feature, 3). deactivate it, 4). switch feature scope to the required one and redeploy it Enjoy!
Read more

Some thoughts on using Sitecore Habitat for Production codebase

Image
Habitat is considered as a demo project to highlight HELIX principles on practice. While Sitecore don’t recommend using it for Production codebase, many sitecoreans still use it as a base for their Sitecore platform projects. There are some people against this and there are lots of supporters. Main arguments of supporters would be that Habitat looks good, have lots of inbuilt functionality and is continuously developed by GitHub community.  Opponents claim that it is bad of using something that is not recommended by the platform vendor. Apart from having some great features, habitat project comes with a set of npm/gulp scripts and free item synchronization framework (unicorn) that allows companies who are building their websites on Sitecore to save costs on early stages of a project. Your dev team would be grateful for having dev setup/deploy scripts that actually work from first attempt (assuming you have the right version of npm and gulp J ). Your finance director w
Read more