I was on one of our web servers earlier today testing something, when I wanted to get into PowerShell. I got in and did what I wanted, but I discovered that PowerShell on this server is version 2. So I asked one of our system administrators if he could put a more recent version of PowerShell onto the server. He said that the version of Management Framework is older and would need to be upgraded in order to install a newer version of PowerShell. I'm a developer, not a sys admin, so I'm taking his word for it. He asked me to test and determine what impact upgrading Management Framework would have. This web server has 2 web sites on it. A third party website and a small MVC web app I wrote, so I don't have a lot of apps to check. I just don't know how to go about it. Would appreciate help, please.
Rod's questions
I have to look at the log files for IIS 7.5 on a Windows Server 2008 R2 server. I've been looking around for something that will help me with that. I've come across several websites that talk about IIS LogParser. e.g.:
However when I look at the system requires here http://www.microsoft.com/en-us/download/details.aspx?id=24659 it only looks Windows Server 2000, 2003 and Windows XP. Can I still use LogParser for Windows Server 2008 R2?
One of our customers is having some problems accessing our web site. They've got 2 machines, and each of them is experiencing different symptoms, but I suspect that even though they're experiencing different symptoms, somehow they might be related to the same cause. I'll discuss the one where I got the most information. On that PC I installed Fiddler 2, and watched the HTTP traffic. I found an add-on that was interfering (something called "Solid Savings") which I disabled. That got me further, but not much. Next I got an error that just stopped me cold; it was an HTTP 504 error. I looked that error up and found that it stands for "Gateway time out". That's nice, but what I don't know is which gateway? Is it our customer's gateway, or is it our gateway?
Alright, I know that this is a very simplistic question, but I'm not sure where else to ask this, and it appears to me via the FAQ, that this is the correct place to ask questions about backup on systems. And since I'm more or less the accidental system administrator, then I'm going to ask.
We have an older Windows AD environment (Windows 2003 R2 Server). We've got a 400 GB Quantum tape drive that we have been using for years to do our backups. We just use Windows Backup and Restore utility for doing our backups. This has worked fine for years. Whenever we have to restore something from off of tape (a very rare occurance) that has worked fine as well. The backup script we use was one deveoloped by the last system admin we had, who left us about 4 years ago (we've never replaced him). I just follow his instructions and that's that.
I've noticed that the backups take about 300 GB on the tapes, so we're doing fine there, with lots of room for additional files. It is that which has me concerned. At our IT meeting today, it was brought up that we should add image files to the backups. (These files are very important documents, which are scanned in.) At this point I don't think that those images are being backed up. I can modify the former sys admin's script to include the relevant files/folders on the server. The server they're being stored on has a huge HD, something like 1 TB in size. Certainly more than enough to overwhelm one of the tapes for that Quantum tape drive. We're probably OK at the moment and will be for a while, but I'm not so sure about the future. If during a backup the tape fills up, will the Windows Backup and Restore utility prompt us to let us know that it needs a new tape? I assume the answer is yes, but I want to double check.
I've got a Dell PowerEdge 2850 server. The display on its front panel says, "BP Drive 2" and that display has an amber color. What does "BP Drive 2" mean?
I've got a server that is very low on disk space, on the C: drive. It's a critical server, that we're working on replacing, but still need to rely on it. In order to free up disk space, I've rebooted it in an effort to get a couple 100 MB back. Normally this works, but today when I attempt to do it, for some stupid reason it is installing some update (I have no idea which one, how large, etc). I'm concerned that there might not be enough disk space on C: to install this update, that it will sit there for hours, perhap says, attempting to install this update, etc. I'd like to know, as a rule, do updates that insist upon being installed, always make certain that there's enough disk space to install, or do they totally ignore irrelevant things like making certain there's enought free disk space so they can be applied?
I'm having to do sys admin work, without the training. (Long story.) We've got a tape drive in one of our Windows 2003 R2 servers. The former sys admin setup a backup job in the Windows Backup and Restore utility, which we've been running, by hand, for a long time. Last week I couldn't be there to fire off the backup job, so I tried to schedule it within the Backup and Restore utility, and I thought that I had. How do I determine that the job ran? I got onto the server, got into the event viewer, looked at Applications for the relevant time period, but didn't see anything. Does that mean it didn't work? Or do I have to look elsewhere?
For years we've backed up our system, using a tape drive on one of our Windows 2003 R2 servers. And we've done this manually. Whenever we do this, we'll put the tape into the drive, and get into the Windows Backup and Restore utility, bring up the saved backup job script, and run it. It always prompts us twice; once to ask if we want to overwrite the data on the tape and to confirm the old save set.
That's nice and all, but I'd like to schedule this so that it happens automatically. I've found on enter link description here an article that describes how to schedule backups using the Windows Backup and Restore utility. So that's great and all, but what about those prompts? I certainly don't want this backup job waiting hours for some human to come along and click the OK button.
I'm standing up a new Windows 2008 R2 Web Server. I've checked the application pool in IIS 7.5, and found that .NET 2.0 is available, but not 3.5 or 4.0. I would have thought that 2008 R2 would have come at least with 3.5 and possibly 4.0. Am I wrong about that?
If I have to install 3.5 and 4.0 on this server, where do I get them? (I'm assuming that it isn't necessarily the same place as client machines get .NET 3.5 and 4.0.)
We've got a new Windows 2008 R2 Web Server. I've got a couple of old, but vital, ASP.NET apps that I'm trying to migrate off of an older 2003 R2 server, onto this new 2008 R2 server. The ASP.NET apps were written using VS 2005. We created a .MSI setup, because we needed to include a Crystal Reports module, which required an installation on the server.
I've copied the .MSI files to the new server, and started to run them, but they fail immediately with a "Installation success or error status: 1603." error (which I got out of the event log, as there wasn't much from the installer, except that it failed).
I've tried looking up this generic error and this is what I can tell you. The SYSTEM account has full control to the drive, folder and .MSI files involved. The drive, folder and file are not encrypted. This is not a substitution drive.
Today I start setting up a new web server for our small, non-profit. Because none of us are sys admins, we're be doing basically what the previous person did, when he set it up on the old server years ago. We have public facing website for our non-profit, what I like to call "brochureware". It describes who we are, where we're located, etc. The previous guy placed this all in wwwroot. Not a folder within wwwroot, just wwwroot. I've always felt that was probably wrong, but I didn't know any better, and I certainly wasn't in charge of it back then. Now that it falls on me, I don't know what I'm supposed to do, so I'd appreciate some help on this, please.
I'm what I guess you might call an accidental sys admin. I don't have the training, and the guy who used to do this left last month, so I'm it.
Before he left, he requisitioned a new Windows Web Server 2008 R2, which just arrived today. So, I've got to put it into the rack and get it joined to our domain. We're using a Windows 2003 R2 Active Directory. Naturally, I want this join this new server to our domain as a member server, but I've never set up a server before, so what steps do I have to do, to get this up and running?
I have to replace a very old UPS. We've got a new one. I'm not really a sys admin, but have to act the part, as the previous one left and, well there's no one else. He had it set up with 2 UPS's, and split the power supplies from each server (5 total) so that 1 power supply went to 1 UPS, and the other power supply went to the second UPS. We've got the new UPS in place. The former sys admin said that the second UPS would be enough to power the servers, while we put in the new UPS. I just want to double check; will this work?
One of my users had a BSOD this morning, so I looked at the event log to see what could be the cause. I didn't find anything obvious related to the BSOD, but I did find something else which causes me some concern. He had the following in his application event log:
Windows cannot access the file gpt.ini for GPO cn={2FE8F71F-F5A6-4829-A6D0-1858E327ED8C},cn=policies,cn=system,DC=amci,DC=unm,DC=edu. The file must be present at the location <\ourdomain\SysVol\ourdomain\Policies{2FE8F71F-F5A6-4829-A6D0-1858E327ED8C}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.
I searched on this website for similar issues, and came across this post. However, this was more for a migration issue. Our servers really haven't changed in at least 3 years. But that post did help explain the fact that I've noticed that GPO's don't seem to be applied anymore. The problem, for us, is that none of us are system administrators. (I did have a class on AD several years ago, but WOW, havne't done anything in it for quite some time.) My question is, do we have an issue with NTFRS, as Tim Long suggests (even though we're not migrating anything, changing our servers, etc)?
I've got a WCF component that I wrote in VS 2008 (using .NET framework 3.5) installed on a Windows 2003 Server. I've been having some problems using one of the methods, and in an effort to try and debug the problem I've been advised to add some diagnostics to the Web.Config file. Now, this WCF server doesn't get used much at all at this point, so can I just make the edits in the Web.Confilg file, and then run a test with my new client app? Or do I have to stop and restart IIS on the Windows 2003 Server?
I've wrote a .NET WCF service I put onto a Windows Server 2003 R2 server several months ago. I've not been able to work with it since, due to other job related responsbilities, but now am trying to get back to it. Back when I did work on it, it worked fine. However, now I'm getting an error message saying that I cannot make a connection to it, from my development machine. That the target machine is "actively refusing it". So I'm wondering if some update, or security patch, applied to the server may now be blocking the attempt. I'm trying to access this via TCP. How do I determine if the TCP port I'm trying to use, is open and listening, on the server?
We have a Windows 2003 Server Active Directory environment. In AD you can enter a person's email address. Back when we used to have Exchange, when creating a new user it would also create an entry in Exchange. We have not had Exchange in years, but when creating accounts, or modifying their profile in AD, I've left the email address portion blank, because I wasn't sure what would happen. Now I'd like to know, can we create an account or modify an existing account, and also add their email address, even if it isn't a part of our domain? (Such as when they have a Hotmail or Gmail account.)
Our management would like to know how people are using our website, which we host on our Windows 2003 Server using IIS. Since none of us are really system administrators, we don't know how to go about getting the information out of wherever IIS, or the system, logs it. Is it kept just in the event logs, or is it some where else?
I just handled a small task, which I would like to automate through Active Directory. We’ve written a few Intranet applications which get used a lot here. Occasionally someone will have to go to the front desk and work on something there, while one of the receptionists are away. They’ll always call us to have us put a shortcut onto their desktop linking to these Intranet applications. It’s just a bit of a nuisance, and I’m sure that AD could be used to automate creating shortcuts on user’s desktops pointing to our Intranet applications. The only thing is, I don’t know how to do this, and being a small shop that we are, we don’t have a system administrator at this time.
So, how do we automate the creation of desktop shortcuts to websites, using AD in a Windows 2003 Server environment?
I've got an ASP.NET application running under IIS on a Windows 7 Ultimate machine, on my home network. However, no one can run anything against it in my home network; whether they're running another Windows 7 machine or Vista. My guess is that I've got to share out wwwroot to everyone (Windows 7 and Vista), but I don't know how. (Sharing on Windows 7 is, to me, the biggest mystery, and headache, I am having with this new OS.)
So, how do I do it?