Hi All,
Does Dameware DRS also use VNC agent to remotely connect to the Windows Workstations ?
At the moment my workstations has got VNC installed and running so I wonder if I can safely uninstall it without affecting Dameware client remote assistance functionality.
Thanks.
Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS. I am using version 12 with both hot patches applied. Other than applying the update nothing had changed in our environment. I can still find computers through the Active Directory, but it isn't nearly as convenient. It is particularly troublesome to find the few computers that are not part of the domain.
Any suggestions for a fix?
Thanks,
Chris
I'm working with central server Dameware 11.1 and trying to get it to work with smart card connectivity in windows 10. It keeps kicking out an error "SmartCard Driver was installed but requires a system reboot (5.5.105.2)." They remote system was restarted in an effort to troubleshoot, however, the event logs do not show anything else other than
System Message: The operation completed successfully.
(srv 64 bit)
Has anyone seen this yet?
The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 5:28 pm
The full text of the message is The Dameware mini remote service is not running on xxx. Would you like to start it now? I answer OK and get "Unable to Start Service; System Error 2; The system cannot find the file specified. It started on a server this morning. After doing a random check of the computers on our domain I have found that it is random. Some machines are ok, some I can't access. It is not dependent on a specific operating system. Can anyone help?
Thanks.
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Mon Jul 09, 2007 6:02 pm
Hello Jodi,
Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?
Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?
Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.
Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.
Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.
For a listing of necessary files, you can take a look at the following KB article on our website:
How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 7:12 pm
Bryan,
The DWRCS.exe file is version 5.1.1.0. We are using 32 bit computers running Windows 2000 SP4 and Windows XP SP2.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest. Some of the machines don't have the file at all.
Our AntiVirus software is Computer Associates and it checks for updates each day and will download them to the individual computers if needed on a daily basis.
Thanks for your help.
Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 3:30 am
Hi Jodi,
You're welcome.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest
Actually, the manifest file is a valid file, so it appears your DWRCS.EXE file has been deleted, not renamed. So this is most likely due to your CA eTrust software, either within the Anti-Virus portion of the software, or within the Pest Patrol portion of the software.
Therefore, all you should have to do is define an exception for our software in either portion of the CA software (AV or Pest Patrol) so it does not delete any files for our software.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 9:33 am
Hi again Jodi,
Here is some additional information I received from another customer on this. Many thanks go out to Zac T. for this information. Hopefully this will help you out:
Here is what worked for me…
1. Log into the E-Trust management console
2. click on the policy management tab at the top of the page
3. under the policies section, change the application dropdown to eTrust PestPatrol and the Type dropdown to Pest Exclusion
4. on the right side of the page change the tab to “Pests” and click the change button.
a. In the box type DameWare and click search.
b. Highlight “DameWare Mini Remote Control” and hit the over arrow so it moves to the Excluded Pests box on the right
c. To close click the “Set Exclude List” button at the bottom
d. Click apply in the Policy Management tab to save those settings
5. Change the tab to “Paths”
a. Click Add
b. Type “Program Files\DameWare Development\DameWare NT Utilities” in the box and click “Set Exclude Path”. (I also added “c:\windows\system32\dwrcs.exe” but I don’t know if that is necessary)
c. Click apply in the Policy Management tab to save the settings
6. the last step is to assign the group to these policies
a. click the “Assign” button
b. navigate to the organization to assign the policy to, move the group to the right and click “assign branches”
that should do it…
This is what worked for us and I hope it helps someone else out that might experience similar issues.
Zac T
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Tue Jul 10, 2007 12:11 pm
Thanks Bryan and Zac T,
We excluded the dwrcs.exe in Pest Patrol and everything is back to normal (at least on the computers we have copied the file back to). Your help has been much appreciated.
Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Wed Jul 11, 2007 6:53 pm
Hi Jodi,
You're absolutely welcome, and thanks so much for letting us know this resolved your issues.
I'm glad we were able to help out.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by wuliping0011 on Fri Apr 16, 2010 8:39 pm
Bryan wrote:Hello Jodi,
Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?
Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?
Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.
Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.
Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.
For a listing of necessary files, you can take a look at the following KB article on our website:
How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000Replica chanle handbags
though that i know a lot.thanks
Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out. I can't get it reinstalled - keep getting the message "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.".
So far, I've tried:
I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs. I can see two DRS10... processes running in task manager, but they never do anything.
Not sure what to try next.
Ideas?
When our IT remotes to our Windows PCs they leave behind the DameWare Development Mirror Driver. This driver causes problems with at least one software application, and so it needs to be removed after the remote IT session is ended. How can this be automated?
Hello All,
So here is my issue. We have over 300 computer that we remote into here at my job. The problem is all of our desktops have dual network connections (wireless & Wired). So when I go to remote into a computer Dame ware automatically connects to the wireless connection and it brings me to the windows login screen. The problem happens when I use the local administrator account to log into the computer. Because the local administrator account does not have Network credentials it can’t connect to the wireless and I lose connection. When I go back in and try to connect to the computer by name dame ware continues looking for that wireless address and never bothers trying to find it on its wire connection that is active. When I go into command prompt and try to ping the computer by name, again it keeps trying to ping the wireless address. The only solution I have found is go out to the computer pull the wired address and then connect directly to it. There has to be a way to connect to this computer after the wireless connection is lost. When I remember to I will log in with my domain credentials pull the wired IP address and then connect directly to it. The problem with that is I don't always remember and then the computer also builds me a profile on the computer that 90% of the time I don't want there. Please help we have been dealing with this issue for a long time and can’t figure it out. Is this a domain controller problem? Is there a way to refresh/ renew IP address on the domain controller? Would that even help? Thanks for every ones help in advance!
A newbe question. Have searched many places and cannot find out what the green icon (by one of my machine IP addresses) means when it becomes green and red. THANKS.
Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am
Hi All,
We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:
Connect Error:
System Error: 10061
System Message: No connection could be made because the target machine actively refused it.
We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.
Any help would be greatly appreciated.
Kind regards.
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am
Hello threeofspades,
Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?
Because a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine.
Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.
However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am
Hi Bryan,
Thank you for your response.
I have some additional information that may help to try to resolve this issue.
I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.
When i try ot connect to the server using MRC i first get a message saying the following:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I select OK but then get the following error:
"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"
When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:
"Could not start the DameWare Mini Remote Control service on Local Computer
Error 2: The system cannot find the file specified."
When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.
I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?
Thank you for your time and effort.
Kind Regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am
Hi threeofspades,
You're welcome and thank you for this additional information. It was very helpful...
As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.
However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.
But you might also want to do a little extra research to find out how this file could have been deleted.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am
Hi Bryan,
I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.
When i tried to MRC onto the server i got the request:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I selected OK and it came up withthe message:
"Service Start Status:
Starting service....."
I thought that this was looking good but unfortunately it came back to the above message:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
It seems that the service is starting but is tehn stopping several seconds later.
I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.
Not sure what is going on but something is stopping the service from running.
Any ideas?
Kind regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm
Hi threeofspades,
Thanks very much for the update. This is some great information.
I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?
If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:
The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am
Hi Bryan,
Thank you for all your help.
We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.
Thanks again for all your help and it was very much appreciated.
Kind Regards
Hello everybody,
we are running the actual version of DameWare 11.1.0.170 for our Administrators to have some smooth remote support ability.
There is only one problem/missed function, we want to have.
We want to see which user is logged into a machine, when we are checking our "Active Computer list" in DameWare.
Also I know this can be done via the Active Directory (add to the description field on the computer), but then we have some double maintenance.
Is there any functionality on DameWare to check which user is logged into. For example is DameWare able to readout the "User and Groups" of Windows or the registry to check whether which user has logged in today?
Thanks for any answer.
Hopefully you can help me.
Best Regards,
Philipp
Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.
DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by dcolpitts on Wed Feb 27, 2008 8:58 am
I've built a support CD that is based on BartPE with Sherpya's XPE plugin interface, using Windows Server 2003 R2 (so SP1) media, that allows us to either boot machines via PXE into BartPE, or using a ramdisk, boot.ini and winnt.sif on the machine's hard drive, boot a copy of our ISO image from a folder. I started out integrating DWMRC into my BartPE image back with version 6.4.0.5. I generally update my ISO image every month or so with the newest DWMRC, antivirus defs, other drivers, etc, and have never had issues using DWMRC until 6.7.0.x. Now when we attempted to connect to the machine booted with BartPE, we are getting the message that theMirror Driver is not able to load, or the machine needs to reboot for it to become active. Yeah, I know we can click by it, but it is a pain, and the performance over DSL to some client locations is less than acceptable.
To integrate DWMRC into the BartPE image, I have created a folder on the ISO image (\Programs\Dameware) and into there, I have placed DWRCK.dll, DWRCS.exe, DWRCSET.dll, DWRCSI.dll, and DWRCST.exe. Next, I've modified the start init for BartPe (actually I'm using Sherpya's XPE interface over top of BartPE) that adds two entries the Microsoft\Windows\CurrentVersion\RunOnceEx key:
%ProgramFiles%\Dameware\DWRCS.EXE -install <-- installs DWMRC + start it
net user administrator clear_text_password <-- creates administrator account and sets it's password as BartPE does not have user accounts as per se
This basically installs and starts DWRCS from %ProgramFiles%\Dameware without adding any files to the %systemroot%\system32 and %systemroot%\system32\drivers folers - and since the ISO image is read only, updating the %systemroot%\system32 and %systemroot%\system32\drivers folders is impossible anyways once it is booted.
So, my question is, what has changed in the mirror driver installation between 6.6.x.x and6.7.x.x and how do I go about integrating the mirror driver of 6.7.x.x into my BartPE ISO. I thought it may just be a matter of adding DamewareDisp.dll to system32 and DamewareMini.sys to drivers, and that they would already be there when the mirror driver tries to install, but that did not help. If I had a copy of the registry entries that DWMRC creates when it installs themirror driver, then I could embedded those in the system hive that exists prior to BartPE booting.
dcc
Dean Colpitts
Members IT Group
Salisbury, NB
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by bryan on Wed Mar 12, 2008 2:46 am
Hi Dean,
Basically nothing has changed in the Mirror Driver itself. The only thing new was the addition of the actual message, letting you know the Mirror Driver couldn't be initialized during this connection for some reason. For example, in a non-standard machine config when the Terminal Services Service has been disabled.
Previously under conditions like this the software would just connect without using the MirrorDriver when it couldn't be loaded for whatever reason. In other words, it would just automatically switch over to non-Mirror mode without notifying you. In this latest version we decided to notify the user of this condition, but all you should have to do is click on OK to continue your connection.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Wed Mar 04, 2009 8:17 am
I used the same method to integrate DWMRC into windows PE 2. After the computer booted from this windows PE CD, DWRCS.EXE was installed fine and DWMRCS service was started as well. From another computer, dameware remote control is able to authenticate to it but the process stucked at "initializing desktop, please wait". This message stayed on screen and dameware remote control could not show the remote desktop. I have tried DWMRC 6.2.x, 6.7.x, 6.8.1.4 and windows PE 2.0, 2.1, 3, but no luck. Did I miss any step or there is some other reason? We are using windows PE CD to image computers at remote sites. It will be great helpful if DWMRCcan work on windows PE CD.
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by dcolpitts on Wed Mar 04, 2009 8:54 am
I'm not sure if this will help you or not, but I use Dameware with BartPE 3.1.10a and here is my plugin files:
CODE: SELECT ALL
; dameware.inf
; PE Builder v3 plug-in INF file for Dameware Mini Remote Control
; Created by Dean Colpitts, Members IT Group
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="Dameware Remote Control Agent"
Enable=1
[WinntDirectories]
[SourceDisksFiles]
Files\System32\*.*=2,,3
[Software.AddReg]
; XPE Shortcuts
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","198","||xpeinit.exe -f -s -m ""Starting Dameware Remote Client"" %Windir%\System32\DWRCS.EXE -install"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","199","||xpeinit.exe -f -s -m ""Starting Dameware Remote Client"" net user administrator password"
Note that the username / password to connect with is saved in clear text within the registry of BartPE and is assigned on the last line of of dameware.inf file.
Below is the script I use to ensure my Plugin folder is update to date from the current installed build on my BartPE compiling machine prior to building a new version of my BartPE image:
CODE: SELECT ALL
rem UPDATE_DAMEWARE_PLUGIN.CMD
C:
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCK.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCS.exe" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCSET.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCShell.dlx" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCSI.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCST.exe" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCST.exe.manifest" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
I build my code from a mounted Windows 2003 SP1 ISO image on my BartPE development machine (actually it's a VM that I do my building in) and I use Sherpya's XPE 1.0.7 plugin for my user interface instead of the nu2menu. I use a default resolution of 1024 x 768 x 32bit.
Once we have the BartPE image created, we then install it into Windows boot loader (or boot.ini) and we also use it with PXE for reimaging / repairing machines at remote sites across the country. This way we can modify the boot.ini remotely to force the machine to boot the BartPE image without any user intervention, or if the machine's HDD is dead / blank / new, we can have the end user PXE boot the machine for us so we can re-image it / repair it as required.
Actually I used these methods yesterday at one client site to install Windows XP on a desktop that we didn't have an image for by invoking an unattended XP setup from within BartPE and once the pc rebooted, it automatically installed XP and joined the domain, where a GPO pushed the Dameware client to the machine and I was able to finish the software installation and customization of the machine.
I know for one thing for sure, BartPE & Dameware have significantly help us cut our response time and costs for reimaging / repairing remote machines.
dcc
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Sat Mar 07, 2009 4:05 am
Hi Dean,
Your method works perfect on BartPE, however windows PE does not like it. I guess MS puts some restrictions on their PE. One benefit of winpe is that it has all device drivers we are using though it is easy to add device drivers to BartPE. I expect some one knows how to fix it on windows pe, otherwise I will switch to BartPE.
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Thu Mar 26, 2009 7:38 am
PCAnywhere Thinhost is able to work well on Windows PE 2.0 and 3.0. Hope Dameware can develop a similar product as well.
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by guy on Tue May 11, 2010 11:58 am
I have not been able to make DW work with any WinPE at all it just saying "Initalzing Desktop. Please Wait...."
I've got a post running here: viewtopic.php?f=9&t=2052&p=5221#p5221
anyone have any ideas?
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by nhelp4k6 on Wed Jun 02, 2010 1:01 pm
I'm curious as to why folks are using mrc (or any similar product) in a PE environment - just not seeing the utility.
The core of WinPE hasn't changed much from 2.x to 3.0, the overview of what WinPE is designed and scoped for can be found here:
http://technet.microsoft.com/en-us/library/dd799308(WS.10).aspx
tl;dr: WinPE is designed to load the OS or prep hw for the OS, not to be the replacement....
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by guy on Tue Aug 10, 2010 5:48 am
The reason I want to use Dameware in PE is that I could remotely boot a PC but then I have no way to dial into the computer and kick off a build or recover a file etc.
Symantec have created PCAnywhere Thinhost for the exact reasons which I want but it's stupidly expensive.
We use Dameware all throughout the Air Force and we will be going to mandated PIV's where we have to use our CAC cards with our administrative accounts, which will prevent us from using Dameware. Is there a work around for this, or will there be a solution for this issue? If there isn't, we will no longer be able to use Dameware and the Air Force will not purchase any more licenses.
I have some questions about the Licensing mode.
Today we use Dameware version 6.8.1.4 with 280 users license and want to change to version 12 and we are not sure to use Standalone License or Centralized Mode.
Standalone Mode
Centralized Mode
We do not need the Gateway and the Internet Proxy. But I think the licensing is much easier.
hello
i have problem with internet session, on server side is everything green
web server is working
https://IP/archi/dwnl/advancedDownload.html?dl=KC1FVK28 i have access to this site
on client side, what link i put in?
Hi,
we are running Dameware Server v11.1.0.163 and DRS v11.1.0.170.
What is the best upgrade path to v12.0?
Should I upgrade the server first, and then the clients? Or the other way round?
Can I update directly from 11.1 to 12.0?
Anything I have to be aware of?
Cheers
Oliver
Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out. I can't get it reinstalled - keep getting the message "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.".
So far, I've tried:
I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs. I can see two DRS10... processes running in task manager, but they never do anything.
Not sure what to try next.
Ideas?
hello support,
i need to found the old version 6.9.0.4 of dameware because want to upgrade the my current license version of this product 6.8.0.4
anyone know where this old version is available ?
very thanks for support
francesco
Dameware install in linux? If not, have hold map for new version for this system operation. ?
Hi!
Tell me please, support server "reverse connection" via the command line.
Thank you.
Why is DameWare Central Server v12 Admin Console using TLS 1.0? Is there a way to change it to only use TLS 1.2?