Sandy's questions

Site 1 has a TZ210 with a content filtered WAN. Site 2 has TZ 105 and an unfiltered WAN. The end goal is to direct traffic from a VLAN on Site 2 to the WAN on Site 1.

From Site 1 I can ping to 10.3.10.4 but not 10.3.10.2. From Site 2 Router I cannot ping 10.3.10.4, but it can ping itself on X4. From the LocoM2 10.3.10.4 I cannot ping 10.3.10.2.

When I direct connect a laptop to Site 2 X4 I can ping the interface.

What steps do I need to take to get these two routers to talk?

This is a similar question to another Serverfault qustion without an answer

I have a SonicWall TZ210 running SonicROM 5.0.2.11. There are two ISPs: ISP A gives a static address and is currently working fine. ISP B offers a cable modem and a DHCP address. The TZ210 connects successfully through ISP A with the static address, but I can't get the TZ210 to receive an address from ISP B.

I have ISB B connected to the X6 port. X6 is in the WAN Zone and set to DHCP but no other configurations have been set. The status for that port shows 100Mbps full-duplex so layer 1 looks solid. I've added X6 to the Load Balance group and removed it with no change.

What steps am I missing to get DHCP working on the X6 WAN Port?

I have both Windows and Apple computers on the same subnet. I have WDS running and I need to add an OS X Mavericks with NetInstall to deploy to Apple products. What configurations do I need to make to allow both systems to boot to their respective deployment systems?

DHCP is running on a Sonciwall TZ 210.

Host is Server 2012 with single Hyper-V guest which is a Domain Controller. When booting the DC it gives a Blue Stop Error: 0xc00002e2 and then reboots. After third reboot it shows a recovery console with options for

*Continue

*Troubleshoot

*Turn off your PC

I choose troublehsoot and open a command prompt and when I tried to run

SFC /scannow

But receive the error: Windows Resource Protection could not start the repair service.

I tried to run chkdsk /r

And receive the error: Windows cannot run disk checking on this volume because it is write protected.

I can boot into DSRM but I'm not sure how to proceed. I try to demote the DC, but receive this error when supplying credentials:

Error verifying credentials: verification of user credential permissions failed. Failed to examine         the Active Directory forest. The error was: The operation cannot continue because LDAP connect/bind operation failed: error 58. Ther specificied server cannot perform the requested operation.)

Server is running 2008R2 with WDS role enabled. Using MDT 2012 I have created a boot image and imported it into WDS.

Client computers can boot from the WDS and it says "Windows is loading files..." and is very slow loading the \boot\boot.sdi, often taking an hour or more.

The slowness only exhibits on the Toshiba laptop clients. Dell laptops have no issue and boot up within a few seconds. What could be causing this and how can I fix it?

I have imported up to date Atheros drivers for the Toshiba and optimized the boot image. I have also created a generic boot image with the same result.

I'm using MDT 2012 to deploy Windows 7 Pro x64. How can I include wireless profiles for several different WiFi networks? There is no domain, all machines are on a workgroup using group policy is not an option.

Is there a Task Sequence, script or other option to automatically connect to WiFi networks?

I'd like to create an account that is not a domain admin, so user cannot log into ADUaC, GP editor, etc but has privileges to access the Event Viewer, install printer drivers and applications on a client PC.

This will be for a student worker to help ease our workload and do basic troubleshooting. How can I create this type of ac

I have a Windows 7 image used to deploy with WDS. We like to install all our applications in the master image. The new Adobe CS6 suite needs to be serialized upon deployment, not in the master image.

I need to run this once upon first boot of the initial deployment. The command to run is:

AdobeSerialization.exe --tool=VolumeSerialize

I know that command works when I run it manually, I just can't get it to run automatically, once, on first boot.

We already have this script that runs and installs our AV client and a few other items: c:\Windows\Setup\Scripts\SetupComplete.cmd

I have copied AdobeSerialization.exe to c:\Windows\Setup\Scripts\ but it does not seem to run.

What's the recommended approach to running this script only once, during first boot?

We are decommissioning around 40 Dell desktops. We would like to donate them but drives need to be wiped. What's the best approach to wipe them all as efficiently as possible?

Is it standard practice to reinstall the OEM OS before donation or is this generally taken care of by the recipient? If I need to reinstall the OS, what's the best approach for imaging 3 different models?

We have a few users running Windows 7 Enterprise. Group Policy does folder redirection for the Desktop and Docs. Users also have to log into a remote server frequently and do not want home folder redirected on that machine. They are not using roaming profiles just home folder redirection.

Is it possible to deny the folder redirection when they RDP into a server?

I have two new models to support, Optiplex 790 and Lenovo L520. I need to add their chipset drivers to the Windows Deployment server and Intel's driver package is a suite of chipset drivers. WDS discovers way too many:

Prior to installing the chipset, SM_Bus shows a yellow exclamation in the Device Manager. When I install Intel's suite, the drivers are installed and SM_Bus is gone. How can I identify which drivers are being used?

Windows Deployment Services on 2008 R2.

I'm trying to add a 64 bit driver package. Dell provides the drivers but they are unsigned. WDS does not allow adding unsigned 64 bit drivers. Is it possible to override this requirement and add them anyway, or is there a simple way to sign these drivers myself?

To be clear, I'm not trying to inject drivers into the boot image, just have them available in the driver pool during installation.

I have a Windows 7 Enterprise PC joined to a domain. Without using any domain level security, how can restrict a certain group of users (students) from logging in, but allow another group (staff) to?