Posted by & filed under General.

So you need to know which users are members of which group… this little PowerShell Script will do the job.

  • Open Notepad and paste the code in below. Save it with the file extension ps1.
  • Open PowerShell with administrator rights.
  • Run the following command the allow unsigned scripts to run locally.

Set-ExecutionPolicy RemoteSigned

Full Documentation here.

Now run the file that you created above, ensure you have a folder on the root of the C: drive called tmp or change the script to your own folder.

It will spit out an CSV file which can be opened in Excel.


Import-Module ActiveDirectory
 $Users = ForEach ($U in (Get-ADUser -Filter {Enabled -eq "True"}))
 {
$UN = Get-ADUser $U -Properties MemberOf
$Groups = ForEach ($Group in ($UN.MemberOf))
{
(Get-ADGroup $Group).Name
}
$Groups = $Groups | Sort
ForEach ($Group in $Groups)
{
New-Object PSObject -Property @{
Name = $UN.Name
Group = $Group
}
}
 }
 $Users | Export-CSV C:tmpUserMemberships.csv

Posted by & filed under General.

Supplied a user with a new printer as the old one had died. She then reported that she couldn’t print PDF’s.  Further investigation reviled that the issue was to do with Windows Server 2008 r2 EasyPrint and Windows XP.  There are many issues related to Windows XP and Easy Print.

This one was a pain to resolve… one of those, easy when you know what is causing the issue.

Remove Advanced Print features from local printer

Navigate to the following location :  Local computer–>Printer Properties–>Advanced tab–> Untick enable advanced printing feature

EasyPrint RDP Advanced

This solution does remove some advance functionality from the printer but not so much to be a show stopper.

Posted by & filed under General.

The other day I was working on a PC and it was low on disk space, on the root of the drive was a Windows.old folder. After backing up the users folder, I started removing the folder due to the Security applied to this folder it can take some time to amend and delete each folder.

After thinking to myself “There Must Be a Better Way” I found the article noted below.  I have noted here for reference.

1. Click Start, in the search box type without quotes “disk cleanup” and hit enter.

2. Select the drive / partition which Windows Vista / 7 is installed on. ( See image Below)

os_select-1

3. It will quickly scan your computer. Then it will display a window like the one below. You need to click “Clean up system files”. If prompted by UAC, then click on Yes. (See image below)

clean_up

4. It will again ask you to select the OS and scan your computer. (See image below)

os_select

5. Make sure “Previous windows installations” is ticked and click Ok. (See image below)

prev_win_inst

6. Click delete files. (See image below)

del_files

7. Windows.old should now be deleted.

Sometimes the contents of Windows.old will be gone, but the folder and some subfolders is still there and undeleteable, because it “Cannot be found”.
If this is the case, try the following…

1. Click Start, in the search box type in without quotes “cmd” and hit enter.

2. Type in….

rd /s /q c:windows.old

and hit enter.

3. The directory should now be gone.

Hope this has helped! :-)

SOURCE: HowToGeek Forum

Posted by & filed under General.

In many businesses the network has been configured for Windows PC’s to connect to a local server for Microsoft Updates. Generally running Windows Server Updates Server or WSUS for short.  If it [WSUS] has an issue and updates aren’t being pulled down, but you need to updated a PC quickly, then you can do the following to turn off WSUS for that PC, which will then allow you to obtain updates directly from Microsoft Servers.

1) Open your registry editor
2) Browse to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU
3) Change the key UseWUServer from 1 to 0
4) Restart the Windows Update service
5) Run Windows Update and it should connect and downloads start

SOURCE:  Eric’s Blog

Posted by & filed under General.

We (Kanzen Solutions and I) ran into an issue with a new laptop the other day.   When trying to install Windows 8  Pro (OEM) onto a laptop which used OEM Activation, the Windows 8 Pro installer pulled the key from the BIOS and once installed was activated as Windows 8 and not Windows 8 Pro.

To get around this issue, you need to create a text file called “PID.TXT” which need to be put into the router of the Sources folder.   To this you will need to created a bootable Windows 8 Pro USB Key, and create the “PID.TXT” onto the key within the Sources folder.

The PID file is formatted like so:

Where the value is the Product Key for your version of windows you are installing.

UPDATE:  You can extract the PID from the BIOS using a tool, located here.

SOURCE: IT Pro Guru, Microsoft Technet

Posted by & filed under General.

Use the following to return all mailboxes and there sizes on a specified database, which outputs to CSV

' Get Exchnage Mailbox Sizes
' Powershell
'
Get-Mailbox -Database "Mailbox Database 2048287781" | sort-object | Select-Object name,alias,servername,ProhibitSendQuota,IssueWarningQuota,MaxReceiveSize,MaxSendSize,DisplayName,Database, PrimarySmtpAddress,ProhibitSendReceiveQuota,@{n="Size(KB)";e = {$MBXstat = Get-MailboxStatistics $_.name; $MBXstat.totalItemsize}},@{n="Items"; e = {$MBXstat = Get-MailboxStatistics $_.name ; $MBXstat.itemcount; $MBXstat.storageLimitStatus}} | Export-Csv C:output.csv
'
'

You can then open the file in Excel and edit to make more readable.

Enjoy :-)

21/08/2013: Updated to make more readable.

Posted by & filed under Article/Opinon.

… Maybe that should be the “IT” world is changing. I thought I was embracing this change. What change am I talking about?

The Cloud.

Recently I received an email from Microsoft to say that the TechNet Subscription is being retired. I was beyond upset. If your an IT Pro, then you know what good value this has been since it’s introduction in 1998 it’s been a great resource, it’s allowed me and many others to legally install and test the latest Microsoft software for a fraction of the cost to purchase the software out right.

In Microsoft’s email, software piracy is given as one of the reasons for it’s discontinuation. I’m not so sure this is valid reason, if it was Microsoft would be killing of MSDN and the Action Pack, would it not?

This is nothing more than a move from Microsoft towards it’s a push to Cloud services, part of it’s new strategy as a services and devices company. For me this is push to soon and too far, a little like Adobe has done with it’s push towards Creative Cloud.

I like many others have given our reasons for our dismay at the discontinuation of the TechNet subscription, with most IT Pros the reason being is to deploy Home Lab’s (as I do myself),  for some, it’s funny to think that IT Pro’s like to geek out at home, isn’t that how this industry started?

My theory is, this is Microsoft’s attempt at pushing us in the direction of embracing The Cloud, (read Azure) then they should introduce Azure TechNet or whatever they may care to call it. A service that allows an IT Pro to use Azure and technologies for a couple of hundred pounds/dollars a year. Where labs could be configured and tested?

Others have suggested a new level of MSDN at a cheaper cost, this would be great too, unless Microsoft see’s the high cost as a barrier to entry and thus a method of stopping piracy.

I for one as many others are,  as evident by this on line petition signed by many IT Pros and growing each day.

Please Microsoft, don’t kick the people that helped you grow into the company that you are today because you want to be more like the cool kids.

Posted by & filed under General.

I was asked to install a printer for a user.  No problem, so I browsed to the server and right clicked the printer and selected connect, then I was presented with a dialogue with the following message, “The credentials supplied conflict with an existing set”.

So I Googled around and came across various links, such as this one and this one.  Then I noticed that I couldn’t open the printer by just double clicking the share, when doing the same to others printers worked OK.

I checked the settings on the server an the user didn’t have access rights to print to that printer.  I added the user and all started working as expected. :-)