Search results for query: *

The problem is solved. The problem was in the backup. There was a storage recovery group active on the original machine, which was included in the backup. This failed the restore constantly because the original database wasn't there yet. We removed the RSG from the original server and then...

Hi all, I'm having the following problem and I just can't get it to work. We're doing a disaster recovery test and we've done the following: * Backup using NTBACKUP for the filesystem and System State. Just to make sure we've included the partitions on which the Exchange database are...

How is the list resolved, using DNS or WINS? With what type of client?

Put it somewhere safe. Log on. Log off. Copy the saved profile over the new profile. Or, use USMT (User State Migration Tool)

Yes you can. Both actually. First one (zeveck's issue): * Create a domain group, say "Techie" and put people in there * Create a COMPUTER startup script with the following line: net localgroup Administrators "<domain\Techie" /ADD Davyd123's issue: Create a COMPUTER startup script...

Give Full Control on the OU containing the computer accounts for the group. Only works if OU's for computers and user accounts are different of course.

Maybe a more effective solution: * Go into users and computers * List all users * Select them all * Choose properties * Set home folder to \\server\share\%USERNAME% or whatever the path is * Apply. This will reset all existing folders and adds the user as with Full Control permissions.

Get IISDIAG (or DIAGIIS) from microsoft. It might help you in detecting problems in your IIS installation.

It also might be that you are using ICS (internet connection sharing). Uncheck that before activating RRAS.

This stuff can be configured for each user in their properties.

I found your problem on the Exchange Experts page, however I'm not a member so I can't read the answer. However, I believe you are running IPv6. Try uninstalling that one and reboot. The Client for Microsoft Networks should be ON. Then try pinging again and show me the results. If they are...

Am I missing something? You promoted a BDC because the PDC crashed. So, now you have two PDC's. One with outdated info, right? Just wipe the old PDC clean and start over and use that machine as the first domain controller.

In fact, AD won't install if you do not use DNS. You CAN however use any DNS server as long as it supports SRV records (forgot the BIND version level but I think it's 8)

RSoP will only report changes to the default behaviour of the system. 14 days is a system default is therefor never logged in RSoP. I'm unsure if it WOULD report it when you change the setting locally. I guess not.

Better would be to use a VPN solution to secure communications using RSA devices.

In WSUS you can create Groups to which clients belong. You can then change the behaviour by approving or declining specific updates for that group. You will however still have to wait for the cycle, but you could set it to an hour and logon as an admin to install the updates.

I've seen two more topics on this. Check those, they might help!

Security GPO's are applied ONLY on the DOMAIN level. If a GPO with those settings is linked to an OU it will apply only to the LOCAL policy, but is overruled by the domain policy. Bear this in mind.

What happens if you ping by IP? What happens if you ping by name? Do you get unexpected results like below? Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms

Ok, but have you CHECKED the setting for me?