locked
Forefront causing long boot times? RRS feed

  • Question

  • We are having an interesting issue. In our computer labs, we have many users that sign in and sign out daily. Obviously this is creating lots of user profiles on these computers.

    A recent issue has popped up where the initial boot time after logging into the domain is taking upwards of 18 minutes to get to the desktop. We have been troubleshooting this issue for the last 2 weeks and have discovered that by disabling MOM service and uninstalling Forefront that the boot times are back to a reasonable 1-2 minutes.

    I know Forefront does not do a boot scan, but is it possible that because the profile either did not exist, or has not signed on since the last computer scan that Forefront is performing a scheduled scan when the new user signs in?

    I do not want to leave our lab computers unprotected, but we can also not have users waiting 18 minutes for their computers to boot.

    If the computer is just logged off and a new user logs in, boot time is normal. This is only occurring with initial boot.

    Any help would be greatly appreciated.

    Friday, October 15, 2010 6:42 PM

All replies

  • They are Windows 7 PC's. I forgot to mention that.
    Friday, October 15, 2010 7:06 PM
  • The October 12th update to Forefront may increase boot times.
    Source:
     
    <Jim at Utica College> wrote in message
    news:7fd70361-a62a-4030-8179-b2e6f493782a@communitybridge.codeplex.com...
    > We are having an interesting issue. In our computer labs, we have many
    > users that sign in and sign out daily. Obviously this is creating lots of
    > user profiles on these computers.
    >
    > A recent issue has popped up where the initial boot time after logging
    > into the domain is taking upwards of 18 minutes to get to the desktop. We
    > have been troubleshooting this issue for the last 2 weeks and have
    > discovered that by disabling MOM service and uninstalling Forefront that
    > the boot times are back to a reasonable 1-2 minutes.
    >
    > I know Forefront does not do a boot scan, but is it possible that because
    > the profile either did not exist, or has not signed on since the last
    > computer scan that Forefront is performing a scheduled scan when the new
    > user signs in?
    >
    > I do not want to leave our lab computers unprotected, but we can also not
    > have users waiting 18 minutes for their computers to boot.
    >
    > If the computer is just logged off and a new user logs in, boot time is
    > normal. This is only occurring with initial boot.
    >
    > Any help would be greatly appreciated.
    >
     
     
     
    Friday, October 15, 2010 7:45 PM
  • This problem has existed prior to the latest Forefront update. I do not believe that is the cause of the issue.

     

    Another question that has come up is about computer scans. We currently schedule scans on Wednesdays at noon to do a quick scan. Does a user have to be logged in for that scan to occur? Does that scan go into effect for each user that logs in or is it only based on the computer? If a user logs out as the scan is running, does it continue running in the back ground?

    Monday, October 18, 2010 8:08 PM