New Post: Discussion begins here
Michelle, Thank you for sharing this solution. Instructions were excellent. In my testing I am noticing a different result than you have indicated. While conducting my testing, I am presented with a...
View ArticleNew Post: Discussion begins here
Hi Raquel,Thanks for posting. I would need some more information about your configuration, your workstation login, whether you are attempting to authenticate to SPD as someone else, etc.Without knowing...
View ArticleClik here to view.
New Post: Discussion begins here
Michelle,Thank you for responding to my post. As mentioned I followed the installation as you have instructed and verified that webpart is in the GAC, registry is in place, security group is created....
View ArticleNew Post: Discussion begins here
Try adding the application pool account to your empty group. I have not conducted any test with an empty group.If you do not want to add any SharePoint user accounts to your group, add a user who does...
View ArticleNew Post: Discussion begins here
Michelle, If I add the app pool account to the security group wouldn’t this mean app pool account can use SPD? Am I missing something? Best Regards, Raquel Contreras From: michelledexheimer...
View ArticleNew Post: Discussion begins here
Read my edited post above yours. Yes, adding the application pool account would give it rights. You do not have to add that account if you don't want. Add an account with no rights on the SharePoint...
View ArticleNew Post: Discussion begins here
michelledexheimer wrote:Read my edited post above yours. Yes, adding the application pool account would give it rights. You do not have to add that account if you don't want. Add an account with no...
View ArticleNew Post: Discussion begins here
FYI to all: Upon further investigation the problem was related to an incomplete deployment. You must deploy both modules according to the instructions provided. In addition, don't forget to activate...
View ArticleNew Post: All users able to access sites in SPD after deploying tool
Hi,We've deployed the tool in our DEV and the QA environment but we are unable to make it work properly.Environment: 1 WFE, 1 CA/Index, 1 SQL Server 2005Product: MOSS 2007 SP2We've deployed both the...
View ArticleNew Post: All users able to access sites in SPD after deploying tool
Do the front end servers need to be rebooted after modifying the registry for the new BlockSPD key to take effect? Thanks. Tom Hockman
View ArticleNew Post: All users able to access sites in SPD after deploying tool
We did reboot the WFE server but has not helped.
View ArticleNew Post: All users able to access sites in SPD after deploying tool
Hi Manish,Sorry for the delay in responding. Everything should work according to the instructions. Please back out all your changes and try again.Who is in the AD group? Are these users all part of the...
View ArticleNew Post: All users able to access sites in SPD after deploying tool
Michelle,The tool is working now after we changed the if condition:Earlier: if (currentContext.Request.LogonUserIdentity.ImpersonationLevel == TokenImpersonationLevel.Impersonation &&...
View ArticleNew Post: Using Block SPD Also Blocks Office Authoring?
Anyone else found that using this module also blocks authoring of documents with Office?
View ArticleNew Post: Having problems on 64-bit Windows 2008
All installs fine. Blocking works great. However, the registered AD Group though recognized does not unblock. There are no errors in the Event logs. Our environments are 64-bit Windows 2008 and IIS...
View ArticleNew Post: Using Block SPD Also Blocks Office Authoring?
Same here. Discovered the issue with this HttpModule long time ago and notified the author ( see...
View ArticleNew Post: Problems with Office 2007
Hi.Currently managing an small farm (2 FrontEnds, 3 on the back). I've implemented the solution, and it works great. But after a couple days, users can't perform all their daily operations.- Edit in MS...
View ArticleSource code checked in, #70298
Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563
View Article
