Showing posts from July, 2011

JoinDomain VMExtensionProvisioningError when deploying WVD (aka Conflict Error)

Deploying WVD Fails with a conflict error and when clicking for more information it presents a conflict and not much else that is useful by way of toubleshooting. Hopefully this helps someone else as it had me head scratching for a little while.. When creating the Host Pool, make sure that you haven't made the fatal error of using the Azure Active Directory Credential INSTEAD of the Local AD Domain Credential.  i.e do not use to domain join, even if it links back to the domain - this is where the conflict arrises.    Instead, use your full internal domain UPN.  Re-deploy your same configuration and you should find it goes through now without any problems. Additional findings.... Albeit my mistake above was an easy one, it does appear the error is directly linked to the domain join process. If you go into your resource groups, locate the session host and MSTSC directly to it.  Try the domain join pr

Implementing an RSS Feed into SharePoint 2010 Foundation

Most people who have reached this page will probably already now know after a while of searching the net that SharePoint 2010 Foundation does not support RSS feeds out of the box. There is however light at the end of the tunnel and we managed to get a number of RSS feeds delivered into our SP2010 site. All you do is as follows: Insert a Web-Part as you might do normally and select 'Content Rollup' then XML Viewer. This is our basis for reading the external feed, edit the new Web Part and enter the external RSS feed into the XML Link box. (You can select test, just to be sure). If you hit Apply your read will show in SP however you'll notice it's not the greatest at displaying the data. So, next step we have to format the text properly. You do this by going to XSL Editor and inserting the code available below: Right click and Save Target as Copy and Paste this code into XSL Editor. Hit Apply and it will format nicely into bullet points, for those of

the signature of the certificate can not be verified Exchange 2003

This took me so long to figure out and there is next to nothing on Google so hopefully this will help a few others like me who have probably reached close to the end of their tether by this point. Everytime we opened the Public Folders section of Exchange this error was produced and so you couldnt then follow any procedures through. Unfortunately for me, I HAD to get into this console. The error is quite simply what it says, there IS an error with your IIS SSL Certificate. Remove your SSL Certificate from IIS and you can access the Public folders, re-add the certificate again and it'll fail again. The ultimate solution is to purchase a correctly signed certificate or if your cushty with CA services, re-issue yourself a shiny new one that matches the server name properly and then install that. Love to know if anyone finds this useful as I spent hours with no results on the net... Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!

A Potential Security Concern Has Been Identified : Access Runtime 2007

We found that in Access 2007 to use a database without the trusted location error bugging the user everytime they open it wasn't quite as simple as you might initially suspect using Access 2007 Pro. To trust a location you have to specify the path in the registry as Trusted Sources / Access Options isn't to be found in the runtime version of Access. Navigate to the following Key: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations Create a string for: 'Path' : Specify the full path to the database (excluding *.mdb) 'Description' : The description isnt relevant but from testing it appears it is required as an entry. Additionally create a DWORD value for 'AllowSubfolders' : 1 to trust any subfolders of Path (Not a requirement) This should eradicate the error from presenting itself, thereby trusting the database. Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!