tosh74

Since recently upgrading to 2004 I have an issue when running fsmgmt.msc when listing sessions on a 2008r2 server. When listing shares and open files it works correctly and quickly. When I attempt to list Sessions the open file pane list about 2 sessions (starting with A's) then sits at not responding, waits a few more seconds, lists a few more but eventually hangs. I have to then force a close and perform the same thing on the 2008r2 server. I can browse the shares no problem from explorer on the Win10 machine. I tend to use this when users call for remote assistance and they have problems reading the machine name from the asset tag Anyone seen this or give me some idea what to look at? Cheers

this is normally done through HPE support/ HPE passport online. If you do not have a HP Passport then create one and register the 5406 to your account. You can then raise a support call to get the module replaced. If you have time you may want to try this. Power down the switch, eject the faulty POE module. Power up the switch again, let it settle then insert the module again. I have seen this clear the fault you described in the past. If not then the module is bust. I would start off the process with HPE first (it may be a day or two before the replacement part arrives) then try the power off/eject/power on/insert - good luck

Other than checking for updated firmware for your 2848 I will have to back out here. good luck

If the phone is plugged into the data vlan it will pick up a data vlan ip. you need something in the data DHCP scope to tell the phone that it should be on the phone vlan instead (option 132 - fromvery quick reading). The phone should change vlan and use the options from your voice DHCP scope or I've totally missed the point

untag your you computer vlan and tag the voice vlan on the port. the rest is done with DHCP options (for reference) https://www.mcgearytech.com/configure-windows-dhcp-for-avaya-ip-telephones/

Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon Computer Configuration\Policies\Administrative Templates\System\Group Policy\Startup Policy Processing Wait Time (default is 30)

https://blogs.technet.microsoft.com/exchange/2017/06/13/net-framework-4-7-and-exchange-server/

Do you have .net framework 4.7 installed on the exchange server? If so remove it and stay with .net 4.5

Try assigning the above script to the machine startup scripts. I am assuming that printers are assigned by room

Hi Andie Sorry for the late reply. The default setting for GPP timout is 60 secs. I normally get away with 20 secs. I never tried lowering it further - like I said try lowering the value to as low as you can get away with

I have had this problem too, and thanks to the help from the guys and gals here at Edugeek, I have managed to minimise this problem. 1st port of call is to increase the number of days the workstation changes it's password (ADUC,Computer Conf, Windows settings,Local policies, Security options) default is 30 days but you can up this (i've seen others suggest 180 days - I disable mine altogether). 2nd increase the Group Policy Processing timeout -start at 60 secs, test and drop this value to as low as you can get away with. This will delay GPP until the wireless card has finished initialising. Only apply these settings to your wirless laptops *Copy the following for an ADM (computer conf). To see this in ADUC correctly you will need to change your filtering setting (view, filtering, untick 'only show policy settings that can be fully managed) CLASS MACHINE CATEGORY "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" KEYNAME "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" POLICY "GpNetworkStartTimeoutPolicyValue" PART "GpNetworkStartTimeoutPolicyValue" NUMERIC VALUENAME "GpNetworkStartTimeoutPolicyValue" END PART END POLICY END CATEGORY *End copy Good luck

Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003. This guide works well for me - start at Prepare the client machine for imaging with Sysprep

Check the DC's Security Logs (as a starting point) and filter by the problem account name

Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003This guide has never let me down for WDS and machine images. Machine names - enter %machinename% into your setpmgr.exe wizard (after deploying you image the machine will boot and start installing. %machinename% is an invalid variable so you will be prompted for a machine name). Windows updates - setup and configure WSUS. Software can be deployed via Software Installation in ADUC HTH

Are your servers and desktops on different subnets? Does your VPN enter on the same subnet as the servers? Most VPN's don't hop across subnets very well

I find this one slightly easier to use than WinstallLE

Handy Free Tools Think this is what you are after

HAW HAW - Last word

Sysprep a Windows 7 Machine ? Start to Finish - The IT Bros Hope this helps

Spot on with the sysprep !! I guess that was the missing part . On my way now. Thanks to both

Cheers. I'll give it a go

@Tommej. not yet. I'm taking a backup of the image before I sysprep it @themightymrp. I am trying to capture the image just now. When I get to the volume to capture screen there are no volumes in the drop down list ( I'll deal with the NIC when I get to that stage) Thanks both for your suggestions

I have injected into both my capture and deploy images. I have change the BIOS from AHCI to Compatible and back. No change. I guess I missing something obvious. Thanks for your suggestions

Anyone managed to inject the correct drivers so we can see the local hard disk to capture the image. I have injected the chipset and intel storage matrix inf files but still cannot see the drive to capture it. Any help appreciated

Microsoft Volume Licensing - Volume Licensing Briefs Read the Reimaging Rights doc