Only tested with IIS 7 on Server 08 R2
- Open ‘CMD’ and navigate to ‘C:\Windows\Microsoft.NET\Framework\<.NET version number>
- Type ‘aspnet_regiis.exe -ir’
- If this is a fresh version of IIS (no other sites running on it) or you’re not worried about the hosted sites breaking with a framework change you can use
-i instead of
- At this point you will see it begin working on installing .NET’s framework in to IIS for you
- Open the IIS management console and click on ‘Application Pools’
- You should now see your ASP.NET version number registered. continue reading…
This applies to Server 2008 R2 and Windows 7 as well, of course. While this may be old news to some, MaxPC had a good article in their latest issue about using symbolic links in Vista. To paraphrase, symbolic links are like shortcuts but at the OS level, not the file system level. Starting in Vista/Server 2008, Microsoft changed the naming convention for user profile folders which would break applications configured to point to these locations (i.e. c:\documents and settings —> c:\users). So to preserve application functionality Windows uses symbolic links to provide a path to get to the new location via the old paths, even though they don’t exist anymore. Look inside any user’s profile and you will see what look like shortcuts to my documents, local settings, etc. These are directory symbolic links. continue reading…
Step 1 – Create the Console
We need to open a hidden console snap-in
- Click Start > Run (or press WIN + R) and type “mmc.exe”
- This opens an empty Microsoft Management Console. Click File > Add/Remove Snap-in… (Ctrl+ M)
- Scroll down the list of available Snap-ins and select Security Configuration and Analysis
- Click Add
- Next select Security Templates
- Click Add
- Click OK
This can be used to find/delete one email or thousands of emails. Again, the below came in handy to zap away the offending emails.
Using Search-Mailbox to search emails
Introducing… the Search-Mailbox cmdlet. This can search for specified criteria and will copy the results to a destination mailbox. First off though, we have to tell Search-Mailbox which mailbox(es) to search – do this using the Get-Mailbox cmdlet.
Error with either Kix32, manually mapping drives, and/or internet issues.
The error I was getting:
‘The mapped network drive could not be created because the following error has occurred: An extended error has occurred.’
– Side note, MS should really rethink the wording on this error.
Run these commands as an admin on the machine:
netsh winsock reset
I strongly recommend against this. Many applications communicate with directory services through LDAP, but the LDAP Request for Comments (RFC) specification stipulates that an LDAP bind should support the passing of a credential. Connecting anonymously really shouldn’t be needed. You may have many Unix-style applications that currently use an anonymous LDAP bind to other directory services, but there’s a good chance that they do actually support binding through a credential, making anonymous binding unnecessary.
Where possible, if anonymous binds are required, create a separate AD LDS instance that allows the anonymous connection and has the subset of information that’s required by the application.
If you have to enable anonymous binds, you can do so.
- Start Adsiedit.msc (Start, Run, Adsiedit.msc).
- Expand the Configuration container. Expand Services, Windows NT.
- Right-click CN=Directory Service and select Properties. continue reading…
In 2008, this is a doddle. Add the user to the built in Event Viewers group!
In 2003 however, there’s a bit more to it. You’ll need to amend the registry. The security of each log is configured locally through the values in the following registry key:
The Application log Security Descriptor is configured through the following registry value:
Replace “Application” in the above path with “System” for the system log,“Security” for the security log etc. continue reading…
It is very common for posters on newgroups to recommend that solution seekers run the “aspnet_regiis -i“ command to fix various problems and ASP.NET maladies. Unfortunately, the -i flag of the aspnet_regiis command does much more than is usually required to fix most problems. It is a sledge hammer when the pennyweight would be a much better choice.
The -i flag causes the aspnet_regiis command to perform its work on every website on the box, not just the one that needs it. As the .NET framework 2.0 begins to ship there will be more developers and production servers running both version of the framework. continue reading…
In IIS6, this was a pain area. On a 64-bit Windows 2003 Server, you cannot run worker processes in both 32-bit mode and as well as 64 bit mode. Either only one of them was possible. This was possible by the below Metabase Key which would be applied to the W3SVC/AppPools node.
W3SVC/AppPools/enable32BitAppOnWin64 : true | false
Read more how to do this in IIS 6.0 here. But, in IIS7, you can run 32-bit and 64-bit worker processes simultaneously. Let’s see how to do it.
You have the same enable32BitAppOnWin64 property for the applicationPools in the applicationHost.config. Now, you can set this for individual application pools. Below is my sample configuration: continue reading…