tramusen

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Security Software #49259

    @raiden89 wrote:

    First post is still incorrect. If you want an accurate list of what works and what doesn’t, you need to modify the list to reflect the programs that actually do work, like the MSE 2.0. A moderator needs to correct this list as Microsoft Security Essentials 2.0 Beta does work.

    It may work, but there is no guarantee that it will continue to work when it comes out of beta. That is important to note as well. Clicking around the Microsoft Connect site, the system requirements links you to the current MSE site, and that states:

    Operating System: Genuine Windows XP (Service Pack 2 or Service Pack 3); Windows Vista (Gold, Service Pack 1, or Service Pack 2); Windows 7

    The workaround for the non-beta MSE (1.x) worked beautifully for a while, and then blew up on an update, telling you that you had an unlicensed copy of Windows. Maybe Microsoft will be kind this time and not do that. Maybe it will not happen until the second or third patch. But it could definitely happen.

    Worse still, if you update it, and it breaks, and then you attempt to uninstall, you may be met with a message that your system is not supported. (OS check wasn’t there when you installed, now it is when you try to uninstall.)

    in reply to: Security Software #49257

    I searched and came back with no hits anywhere, so I’m going to post this without browsing all 7 pages. Sorry if I missed it…

    Microsoft Forefront Client Security just works, and from what I can tell you get the full version if you install the client from the trial. Sign up for the trial, get the image, and then do the following once you have it mounted or burned:

    Open command line as admin
    If you have x64 (assuming this as this is for R2) and using D: as your image, then run:
    D:CLIENTX64CLIENTSETUP.EXE /NOMOM

    If you happen to be running x86:
    D:CLIENTCLIENTSETUP.EXE /NOMOM

    The /NOMOM option installs it so that your copy points to Microsoft for updates, rather than a Forefront server.

    It will install, then you can update through MS Update. Works just like Security Essentials, and you don’t have to worry about whether the final of 2.0 breaks compatibility, as compatibility eventually broke with even the hack method to get the old version installed.

    I believe this will run “forever,” though I haven’t done anything like comparing files between the trial image and the Technet-sourced image I have now. As FCS is more (entirely?) focused on businesses that also want the server-side management tools, I wouldn’t be surprised if there isn’t any licensing wired into the client, as if you don’t pay for your licenses as a business it is much easier for a company to come down hard on you. The server software also is pretty expensive, so the per-client license seems more like the icing on the cake than the real source of income.

    Sure, you can get MSE to work, at least for now. Or you can use some other supported virus scan. But this is free (as best as I can tell, YMMV, someone feel free to correct me if I am way off on this), and if you happen to like MSE, this is basically the same thing with a different name.

    in reply to: Running as Administrator #51173

    While that works for MOST user documents / data, it leaves out the hidden AppData folder, which is unfortuantely where a lot of the bloat winds up getting placed. Google Chrome stores all of its data there, and Outlook puts your mailboxes there by default. Some half-hearted searching for how to move my Gmail IMAP mailboxes turned up empty, and I don’t know that you can move the Chrome data, so rather than hassle with it I just redirected the whole profile folder. Just to give some perspective, in about two days of use my AppData folder has already reached 1.5GB. I don’t expect this rate to persist, but that’s still a pretty quick climb.

    I suppose I could have junctioned only the AppData folder with the previous steps, but that just felt messier than doing it up one level.

    edit – I think it may be possible to configure the system to place all profile folders in a different location, but I believe that is more for Active Directory purposes than anything else. I didn’t want to take the time to research it before having my system up and running, may revisit it as I have time.

    I’m leaving my programs installed on my OS drive, since there are so few. I haven’t done much looking at the ProgramData folder, it can probably stay as well, though I have seen people moving that to a different drive along with the AppData folder. Other than fairly lightweight utilities, I don’t have any need for much else. Eventually, Visual Studio, but not right now. Right now I have 47.3 out of 59.6GB free, so a nice big cushion in case I do happen to install anything moving forward. Outlook takes a little while to load, since all the mailboxes are on the 500GB, but Word loads in about a second. Much better than before the SSD.

    Games I’m installing through Sandboxie, and I’m installing them on a 500GB SATA drive. Keeps them as far from the OS as possible. Not perfect, but safer than it could be.

    in reply to: Running as Administrator #51171

    @halladayrules wrote:

    As far as migrating your user profile from one drive to another, have you tried Easy Transfer? I was able to get it working here.

    Isn’t this just for moving from an old computer / drive to a new one? If there is a tool, especially a MS-provided one, that lets you move your user folder to a secondary drive I would rather do that than go with a hard link.

    Just remembered how I did that to begin with, so I will post it here. I think this is the source I started with:
    http://justenoughtechnology.com/move-user-profile-to-2nd-drive-in-win-7/

    To (attempt to) summarize:
    Make account with Administrator account > log out
    Log in to new account > shut down
    Boot to install CD to command line
    Use robocopy to duplicate user folder onto target drive
    (For example, calling it X:PATHTOusername)
    Delete (or back up?) user folder from source drive
    Create link using “mklink /J C:usersusername X:PATHTOusername”
    Reboot and log in to new account

    That got me set up with my main, non-default account storing data on a secondary drive. Keeps all of my user folders from accidentally ballooning and overloading my SSD.

    in reply to: Running as Administrator #51167

    The firewall is something I have been exploring for a while. I’m assuming you mean something a bit more robust than just a router, including those with something like DD-WRT running on them? This is all for home personal use, and I don’t have a lot of pocket money to invest on a commercial firewall appliance. Any software solutions worth looking into? Any reasonably priced hardware? Is slightly dated hardware worthwhile? (I’m thinking Craigslist for that.)

    Already had taken care of the other two. I don’t follow the scanning as carefully as I probably should, but I also don’t download all that much. That which I do is usually from reputable locations, though I know assuming that that is sufficiently safe isn’t the best idea.

    Just in case anyone is reading through this thinking the same thing about just using the built-in account, there are reasons not to use the admin account. The one I recently came across was moving profile data to a different drive. I have a 64GB SSD as my boot drive, and don’t want to have all of my profile information and my AppData folder on there. Setting this up was easy enough for me, it involved making a junction and a few other things that are likely detailed very nicely in a tutorial somewhere. Setting this up with the administrator account seemed like a bad idea. So I made an account in the Admin group and set it up to be in the correct location. That way, if anything breaks in a horrible way I can still log in to the default Administrator account to try to fix it. Just one example, specific to my situation, but I am guessing there are many more where that came from.

    in reply to: Security Software #49227

    This workaround was fantastic, the first time. Now I’m getting an error.

    First installation: Trial copy of WS2k8R2 during activation grace period
    Used WinDBG method, everything great.

    Second installation: License came in mail, so did a clean install. Used same method, first attempt said Windows not valid. Panicked, went to Microsoft’s site, checked to make sure, yes it is valid. Tried to install again, it worked, but a message popped up saying I had 30 days to get genuine before MSE shuts down.

    Any ideas? Is this a new version of the installer causing this? I have the old installer stashed somewhere on an external drive, I think, but if I simply did something wrong, I would rather uninstall / reinstall than deal with that.

    EDIT: Tried uninstalling… can’t. Says that I’m running an unsupported OS. Tried a few things like using WinDBG similar to the install to see if I could uninstall using the setup file outside of the add/remove programs dialog, no luck. Anyone have any idea on how to at least do that? (NOTE – Reinstalled, so that part isn’t necessary for me at this time, but others may find it useful)

    UPDATE – Ok, got it installed. Had to do two things:

    1. Do not install any updates. (Using 2 with all updates failed for me, must be multiple issues…)
    2. Instead of the WinDbg steps from the linked blog post above, used the steps posted here:
    http://vspug.com/jeff102410/2010/02/06/install-microsoft-security-essentials-on-windows-server-2008-r2/
    Note: the only change is that ctrl+break isn’t used. The breakpoint is set, g is used to run the program, and it is left running.

    In hindsight, I didn’t use the exact steps posted in this thread, they might work just fine.

    Something about using the first method was preventing the installer from being seen as validated, and something about one of the updates kept the software from seeing windows as valid once installed.

    Now that MSE is installed and working, I am installing updates to see if that breaks things.

    What is still needed – a good guide for removing the software. Just in case some update causes just what I experienced, MSE failing for one reason or another. Rather than reinstalling Windows, it would be easier to just uninstall MSE. I don’t even know where to start on that, though I hope to poke around at it as I have time. Hoping someone more knowledgeable on it might already know the answer, or a large chunk of it.

Viewing 6 posts - 1 through 6 (of 6 total)