I spent hours looking for a solution. I was missing the BitLocker Recovery Tab in Active Directory Users and Computers (ADUC) on Windows 7. Honestly, there are a lot of posts about this…but almost all of them detail how to do things in Windows Server 2008 and Windows 7 is nowhere to be found. Of course, I tried to use them for Windows 7…but nothing worked.
The problem: I was missing the BitLocker tab that displays the BitLocker recovery key for Active Directory Users and Computers. No amount of DLL re-registering or Remote Server Administration Toolkit (RSAT) installing (those 2 are solutions in Server 2008) helped me display that tab.
When I finally did solve this problem, I found I was very close the entire time…and it was simple. As the saying goes, that only counts in horseshoes and hand grenades. I found the simple solution by my non-Sherlock Holmes power of deduction….I knew BitLocker was a part of RSAT from Microsoft and so I figured that viewing the tab might be a feature add-on…and my suspicion was absolutely right. Screenshots of everything for a visual representation of this solution below.
Note: You must install Remote Server Administration Tools (RSAT) for Windows 7 before the feature we need to enable will become available. Install that first, then come back here and perform the following steps:
That’s it. Now when you go inside ADUC, you’ll have a recovery key tab available on PC’s you’ve encrypted using BitLocker. All that fuss and hunting for a solution that takes about 3 minutes to fix. Simple right? I sure hope that in publishing this, I make it more readily available and searchable for those looking for the solution in the future…because it sure took me a long time to find it! Thanks for reading!
I could go on and on but I figured I’d need to stop somewhere. It’s pretty bad. It seems users have been reporting this even a few months before I tested it out in September 2010…so this problem has been around for more than 6 months and RIM hasn’t done anything to fix it…and they wonder why Android is chewing up their market?
The worst thing is that when googling around this particular error…you find it is a simple fix in .NET framework inside the application and the app just needs a reference fixed and a recompile. Figures. Something that could be done simply and quickly to solve pain and suffering of many goes unnoticed…but hey, let’s make sure we make big bucks on everything else!!
Bottom line is…I have to revert back to previous version. This means I can’t update my BlackBerry and I can’t call customer service because they won’t help me unless I’m running the most recent version. So at least they have THAT going for them…they don’t have to address any concerns about BlackBerry Desktop Manager 6 because they can just ignore people that call in that aren’t running that version of the software…and since the people CAN’T get to that version, they get lost in the void.
Hat’s of to RIM! They’ve cooked up a good way to ignore people in this case. I hope they fix their problem sometime in the next 6 months.
I hit a snag at work today while trying to create a scheduled task to run a batch file daily on a server. The problem was after creating a scheduled task using the wizard, a popup displayed this:
The new task could not be created.
The specific error is:
0x80070005: Access is denied.
Try using the Task page Browse button to locate the application.
Of course, the task wasn’t created. Googling around wasn’t much help…most of the stuff references Windows XP and a bunch of the results want you to go inside the registry. I figured there must be a better way. Something that all the posts had in common was saying that something had changed the permissions on the Windows Tasks directory. So, I figured running CACLS to reset the permissions on that tasks directory should fix things. I was right. So this fix is MUCH simpler than all those forum posts and mailing lists posts said.
To fix: Open up a command prompt and change directory to C:\WINDOWS. Next issue the following command:
CACLS Tasks /E /G builtin\administrators:F
it should echo back ‘processed dir: C\WINDOWS\Tasks’ and return you to a prompt. After this, you should be able to schedule a task quite easily. The skinny of this problem is that the tasks directory just gets its permissions wrong and you’re using CACLS to reset things. Hope this helps someone out there! It took me a couple hours to figure it out!
I’m getting pretty used to powershell in my day to day workings with Exchange. Today however, I was helping a user out on a PC in a different department and I needed to find all of the members of a specific security group. Sure, I could remote back into my work PC and launch ADUC but I’d rather be able to query it with a single query…all from right there using her computer with the limited user account.
Thanks to powershell, I now think in pipes…while I’ve always done this with Linux, I’ve never had to do so with Windows. It’s almost like wearing two caps at the same time. Nonetheless, I was able to figure out how to do this after 3 or 4 attempts and then output it to a file so I could see members of the security group and I did so without the power of powershell (ba-dum-ching!)
I used dsquery and piped the command using dsget to grab the information I needed and then output that into a text file onto the desktop. Important to note that you should open the command window using ‘run as’. So in XP, browse to Start >> Programs >> Accessories and then right click ‘command prompt’ and ‘run as’ with elevated privileges. You’ll need to be able to view the group you’re querying. I used my own user since I’m a domain admin…you get the idea. Once you have the command prompt, cd to Desktop so the text file will be easy to find. Then initiate the following command:
dsquery group -name GroupName |dsget group -members |dsget user -display >memberlist.txt
Substitute for GroupName and put in the group you’re looking for. Hopefully this helps out.