Local Director Remote Management

Is there any way to use SNMP to manage the Local Director. I have the SNMP community but I can't seem to change the server status from out of service to in service using snmpset (from UCD-SNMP). Am I doing this in vain. Are there any ways to do remote management of the LD or can it easily be scripted. Thanks.

you cannot SET values for the Local Director through SNMP. Just GET them.
There used to be a GUI for the LD, that works up to version 3.x. It no longer works in version 4.x. The name for it is CVS and it can take servers out of service. It does it by telnetting to the LD and issueing commands.
Also, the LD support Dynamic Feedback Protocol (DFP) which is a protocol that allows the LD to talk to an agent application (installed on the server) and can dynamically adjust the server weight according to load.
Hope that helps,
-Steve

Similar Messages

Steps to setup and configure Node Manager on local and remote machine

Hello,
I am using WLS 10.3 on Windows.
I have two machines, One cluster and two managed servers (one on each machine) created under a domain. I have used configuration wizard to create the domain.
I have gone through documents on Node Manager and found what to configure. But I have not found when to configure. In other words I want to know what is the sequence of steps if I have to set Node Manager on my local machine (in which domain exists) and on remote machine.
Please let me know the sequence of steps I need to follow to set and configure the Node Manager on local and remote machine. I want to use Java Node Manager (not the Script node manager).
Thanks,
Sanjay

Hello,
Ok, let me tell you what I have done till now.
1) Installed WebLogic 10.3 on machine A (local machine, on which I have created domain and my Admin Server is running. Also Managed Server 1 is created on this machine).
2) Installed WebLogic 10.3 on machine B (remote machine, on which Managed Server 2 will be created).
3) On machine A I used the configuration wizard and create a domain. While creating the domain I did the following:
i) Created two managed servers.
ii) Created a cluster
iii) Assigned Servers to cluster.
iv) Created two machines.
v) Assigned servers to machines (Admin Server and MS_1 to machine A and MS_2 to machine B).
4) Sarted Admin Server.
5) On the Admin Console I made some configurations for the Node Manager on Machines -> Machine A -> Node Manager. Assigned the values:
i) Type (SSL)
ii) Listen Address (IP_Address of machine A)
iii) Listen Port (5556)
6) Similarly did for Machine B.
So till now phsically the managed server (MS_2) directory and configuration is not there on Machine B (its only configured on machine A because I created the domain on Machine A).
Now I want install/configure/setup NM on both the machines. Start my both the managed servers using Admin Console (which will use the node managers).
What are the sequence of steps I need to follow my task?
Any help and suggestions are welcome with warm regards.
Thanks,
Sanjay

Synchronizing local and remote sites

Greetings
I created a site locally and then FTPed it up to a server at
my ISP. The site was working fine until I made a number of changes
that I note below. When in DW and I try try to preview in a
browser, I am unable to view any of the files in any browser
because DW is unable to locate the files locally and remotely.
The error message I get is:
Firefox can't find the file at
/______/______/_____/_____/ThankYouVeryMuch/Website/tyvmi
3/index.htm.
The changes that were made to the site:
- I reorganized my folders locally thereby creating a new
root folder. When I tried to add 3 pages, I received several error
messages. One of them was that DW was unable to locate the home
page. Another was that it was unable to create the site map and if
I'm not mistaken DW was unable to create cache files.
- My client had a friend add some Google analytics to the
site. This person also created an XML site map. Obviously, the
local and web sites were not synchronized so I was receiving more
error messages.
- I then downloaded the site to a new directory in the new
root folder I created above. This downloaded site is my local root
directory in the Site manager and is located at
./______/______/_____/_____/ThankYouVeryMuch/Website/tyvmi
3/index.htm
- These are my current directories for the site
thankyouverymuchinc.com:
Site name: Thank You Very Much Inc
Local: ThankYouVeryMuch
----------> Website
-------------> tyvmi 3
---------------> index.htm
---------------> pages
Remote: host: ip address
----------> www/htdocs/
---------------> index.htm
---------------> pages
Many thanks
Marlene

Do you have a testing server defined?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"troika22" <[email protected]> wrote in
message
news:[email protected]...
> Greetings
>
> I created a site locally and then FTPed it up to a
server at my ISP. The
> site
> was working fine until I made a number of changes that I
note below. When
> in DW
> and I try try to preview in a browser, I am unable to
view any of the
> files in
> any browser because DW is unable to locate the files
locally and remotely.
>
> The error message I get is:
> Firefox can't find the file at
>
/______/______/_____/_____/ThankYouVeryMuch/Website/tyvmi
3/index.htm.
>
> The changes that were made to the site:
>
> - I reorganized my folders locally thereby creating a
new root folder.
> When I
> tried to add 3 pages, I received several error messages.
One of them was
> that
> DW was unable to locate the home page. Another was that
it was unable to
> create
> the site map and if I'm not mistaken DW was unable to
create cache files.
>
> - My client had a friend add some Google analytics to
the site. This
> person
> also created an XML site map. Obviously, the local and
web sites were not
> synchronized so I was receiving more error messages.
>
> - I then downloaded the site to a new directory in the
new root folder I
> created above. This downloaded site is my local root
directory in the Site
> manager and is located at
>
./______/______/_____/_____/ThankYouVeryMuch/Website/tyvmi
3/index.htm
>
> - These are my current directories for the site
thankyouverymuchinc.com:
>
> Site name: Thank You Very Much Inc
>
> Local: ThankYouVeryMuch
> ----------> Website
> -------------> tyvmi 3
> ---------------> index.htm
> ---------------> pages
>
> Remote: host: ip address
> ----------> www/htdocs/
> ---------------> index.htm
> ---------------> pages
>
> Many thanks
> Marlene
>

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012
The following guide will enable you to:
1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager
! This should also work for Core installations of server 2012, but I haven't tried.
This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.
* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.
- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.
> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)
1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.
! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012
2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.
> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
> Next, is to get the MMC firewall snap-in working.
The reason for this, is to have a GUI available to configure it.
If you're happy without it, you may skip this and use a shell instead to do so.
? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)
! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level
# (In other words: allows the firewall to be remotely managed)
! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.
? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.
! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done
! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon,
# and choose run as admin on the bar below.
! Client: application MMC: select "file" --> Add/remove snap-in
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)
* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.
! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.
! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.
! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate
# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
# I recommend to choose yes; unless you like to pull some more hairs...
! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
! select yes
! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server
Done.
You can now manage your remote server through the familiar computer management GUI.
! Right-click your remote server, and select "Computer Management"
A few side notes:
? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.
If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.
Cheers!

As a little update to the post, I'd like to add that replication, clustering and migration will not work in workgroup environments. Unless someone can provide an additional guide for this, I'd recommend anyone to no even bother to try.
To manage the standalone hyper-v server in a remote location over the internet, I would recommend the following:
Install windows 8 pro (x86 uses less resources!) as a vm on the host, and assign 2 network connections to it.
1 external (shared with host) (be sure you have a dedicated ip-address for it!)
1 internal connection.
What I did was this:
As soon as you've installed the win8 guest, proceed with the guide as described.
For the 1st step of the guide (hosts-file) use the ip-address you will later assign to the "internal" network switch of the host!
In my example, I'm using 10.0.0.1 for the host, and 10.0.0.2 for the guest.
To be clear: I first used the guide on a LAN-environment, and did all the steps from a "real" client to server on the LAN.
Then, installed the win8 guest on the host using the "real" clients' hyper-v manager over the LAN.
Next, assigned the 2 network connections to the VM, and configured them as follows:
external - as you would to be able to make your guest reach the internet.
internal - I used the following config:
ip-address: 10.0.0.2
subnet: 255.255.255.252
gateway - blank
dns - Blank
Now, when you get to the console of the hyper-v server (host) or RDP to it, go to network settings.
You'll see that the internal card has been added here as well.
Configure it as follows:
ip-address: static - 10.0.0.1
subnet: 255.255.255.252
gateway - blank
dns - blank
You should now be able to ping your guest (win8) on 10.0.0.2 if it's running.
Don't forget to enable ping response (option 4 on the host) to test connectivity the other way around as well (guest to host)
When you're done, you'll be able to RDP to the guest OS over the internet, and then connect to the host with server manager, hyper-v manager, and MMC.
Don't forget to enable each module on the hosts' firewall to make the snap-ins work!
Remote volume management requires your guest/client firewall INcoming ports to be enabled as well! not just the host.
Either update the firewall rules from the MMC gui as described in the guide, or use the following commands on the
hosts' powershell:
Enable the firewall rules with the command Enable-NetFirewallRule -DisplayGroup "USE_THE_COMMANDS_BELOW" (include the " " in the command)
Remote Service Management
Remote Volume Management
Remote Event Log Management
Remote Scheduled Tasks Management
Windows Firewall Remote Management
Windows Remote Management
You can get the list with Get-NetFirewallRule -DisplayName *management*
You can get the list with Get-NetFirewallRule -DisplayName *remote*
Commands provided with credits to F. verstegen
Cheers,
Michael.
Sigh...

Remote Management of Hyper-V Across One-Way Trust

In order to abstract our hardware from the platform, we would like to virtualize all of our physical machines, installing Hyper-V server and just running one VM on Hyper-V. We hope this will allow us to quickly migrate machines that currently cannot be on
our virtual environment for whatever reason.
We set up a management domain for all of the Hyper-V servers separate from our main domain. A one way trust was established between the main domain and the management domain, with the management domain trusting the main domain. On the management domain,
we created a domain local group, called Management Domain Admins, which contains the foreign security principals from the main domain. The Management Domain Admins group is added to the Hyper-V built in Administrators group.
Now here is the problem, from a workstation in the main domain, we can manage every part of that server except for adding a virtual hard disk. We can manage the firewall, we can look through the event log, we can create virtual machines and connect them
to existing virtual hard disks, but we cannot create a virtual hard disk. The log returns:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
We disabled the firewall on both the workstation and the server with the same result. Using a workstation WITHIN the management domain, logging in with an account from the main domain, we can create a virtual hard disk. We have also tried enabling anonymous
DCOM and adding the Hyper-V server to the Trusted Hosts list in WinRM to no avail. Also, using inline authentication, we can create virtual hard disks on the server BEFORE adding it to the domain. But as soon as it's added to the domain, we can no longer create
hard disks.
Appreciate any insight!

I hope it isn't the trust and it's something dumb I forgot to set. I checked again and "cscript .\hvremote.wsf /anondcom:grant" returns "INFO: Nothing to do - ANONYMOUS LOGON already has remote access"
Thanks!
The event is generate from DCOM, 10028
DCOM was unable to communicate with the computer <myserver> using any of the configured protocols; requested by PID a34 (C:\Windows\system32\mmc.exe).
The full trace is:
2013-07-24 07:59:24.988 [15] USER_ACTION_INITIATED Wizards NewVirtualHardDiskWizard:CreateVirtualHardDiskOnBackgroundThread() Creating new virtual hard disk ...
2013-07-24 07:59:24.997 [15] USER_ACTION_INITIATED VirtMan ImageManagementServiceView:BeginCreateVirtualHardDisk() Starting creating dynamic virtual hard disk 'D:\Hyper-V\Virtual Hard Disks\test.vhdx' (size = '136365211648')
2013-07-24 07:59:26.645 [15] ERROR Wizards VMWizardForm:PerformWizardActionInternal() Failed to perform wizard action!
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementBaseObject.get_wbemObject()
at System.Management.ManagementClass.CreateInstance()
at Microsoft.Virtualization.Client.Management.VirtualHardDiskSettingData.GetVirtualHardDiskSettingDataEmbeddedInstance(String serverName, String namespacePath)
at Microsoft.Virtualization.Client.Management.ImageManagementServiceView.BeginCreateVirtualHardDisk(VirtualHardDiskType type, VirtualHardDiskFormat format, String path, String parentPath, Int64 maxInternalSize)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.CreateVirtualHardDiskOnBackgroundThread(Server server, VirtualHardDiskFormat hardDiskFormat, VirtualHardDiskType hardDiskType, String filePath, ConfigurationInfo configBase)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.PerformWizardAction(Object stateObj)
at Microsoft.Virtualization.Client.Wizards.VMWizardForm.PerformWizardActionInternal(Object stateObj)
2013-07-24 07:59:26.754 [16] ERROR Wizards VMWizardForm:WizardActionFailed() Wizard action failed!
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementBaseObject.get_wbemObject()
at System.Management.ManagementClass.CreateInstance()
at Microsoft.Virtualization.Client.Management.VirtualHardDiskSettingData.GetVirtualHardDiskSettingDataEmbeddedInstance(String serverName, String namespacePath)
at Microsoft.Virtualization.Client.Management.ImageManagementServiceView.BeginCreateVirtualHardDisk(VirtualHardDiskType type, VirtualHardDiskFormat format, String path, String parentPath, Int64 maxInternalSize)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.CreateVirtualHardDiskOnBackgroundThread(Server server, VirtualHardDiskFormat hardDiskFormat, VirtualHardDiskType hardDiskType, String filePath, ConfigurationInfo configBase)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.PerformWizardAction(Object stateObj)
at Microsoft.Virtualization.Client.Wizards.VMWizardForm.PerformWizardActionInternal(Object stateObj)
2013-07-24 07:59:26.755 [16] ERROR Client InformationDisplayer:GetErrorInformationFromException() Application encountered a non-VirtMan exception! Not going to display non-localized message to user.
2013-07-24 07:59:26.756 [16] ERROR Client UnhandledExceptionHandler:HandleThreadExceptionInternal() Application encountered an unexpected exception!
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementBaseObject.get_wbemObject()
at System.Management.ManagementClass.CreateInstance()
at Microsoft.Virtualization.Client.Management.VirtualHardDiskSettingData.GetVirtualHardDiskSettingDataEmbeddedInstance(String serverName, String namespacePath)
at Microsoft.Virtualization.Client.Management.ImageManagementServiceView.BeginCreateVirtualHardDisk(VirtualHardDiskType type, VirtualHardDiskFormat format, String path, String parentPath, Int64 maxInternalSize)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.CreateVirtualHardDiskOnBackgroundThread(Server server, VirtualHardDiskFormat hardDiskFormat, VirtualHardDiskType hardDiskType, String filePath, ConfigurationInfo configBase)
at Microsoft.Virtualization.Client.Wizards.NewVhd.NewVirtualHardDiskWizard.PerformWizardAction(Object stateObj)
at Microsoft.Virtualization.Client.Wizards.VMWizardForm.PerformWizardActionInternal(Object stateObj)

System Image Utility - Create User - Activate Remote Management

When creating an image with system image utility, based on a DVD image instead of a cloned image, I cannot create a user and activate Remote Management.
I have created an installer package with Apple Remote Desktop that is supposed to do both, however it doesn't work. I do not get an error, but no user is created.
I have tried a post-install script however the dscl command is not recognized even if I put the path /usr/bin/dscl.
I even tried to use a popular package out there called "createUser" but that fails as well.
Has anyone had any luck with this when trying to make a moduler image with System Image Utility?
Message was edited by: NeedSomeAnswer

After configuring all the appropriate settings, I
push the "Create" button and it appears to start
working, prompts me for a location to save the actual
image itself, creates a folder with the default name
and then nothing happens.
ok here's the deal: i created a folder in my OSX server home directory labelled "images" and keep our multiple images there. although you CAN have your images on other drives or on the network, that would take a LOOOOOOOONG time to do the data transfer to the invisible netboot folder on your server. my advice: keep local copies of all images. save a ton of time for yourself, eh?
then, when it's time to use the system image suntility to load up an image, i go to that same location each time, call it up and have the app set to the prefs i want or need. i'm on 10.4.7 server and have had no problem using the software.
so try using images locally and then, if that doesn't work, upgrade to 10.4.7

[Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

As we all know,
the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
Essentials Experience role in Server Manager or via Windows PowerShell.
In this article, we introduce the steps to install and configure Windows
Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
Before installing the Windows Server Essentials Experience Role, please use
Get-WindowsFeature
PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
Figure 1.
Part 1: Install Windows Server Essentials Experience role locally
Add Windows Server Essentials Experience role
Run Windows PowerShell as administrator, then type
Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
Figure 2.
Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
(Figure 3)
Figure 3.
2. Configure Windows Server Essentials Experience role
(1) In an existing domain environment
Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
Figure 4.
After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
Server Essentials:
Start-WssConfigurationService –Credential <Your Credential>
Note: The type of
Your Credential should be as: Domain-Name\Domain-User-Account.
You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
Figure 5.
Next, you can type the password for the domain account. (Figure 6)
Figure 6.
After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
Figure 7.
By the way, you can use
Get-WssConfigurationStatus
PowerShell cmdlet to
get the status of the configuration of Windows Server Essentials. Specify the
ShowProgress parameter to view a progress indicator. (Figure 8)
Figure 8.
(2) In a non-domain environment
Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
Figure 9.
After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
Figure 12.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Part 2: Install and configure Windows Server Essentials Experience role remotely
In an existing domain environment
In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
Add-WindowsFeature -Name ServerEssentialsRole
-ComputerName xxx -Credential DomainName\DomainAccount
Figure 13.
After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
Figure 14.
After the installation completes, it will return the result as below:
Figure 15.
Next, please use the
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
Enter-PSSession –ComputerName
xxx –Credential DomainName\DomainAccount (Figure 16)
Figure 16.
Then, please configure Server Essentials Role via
Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
Figure 17.
After your credential is accepted, it will update and prepare your server. (Figure 18)
Figure 18.
After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
Figure 19.
2. In a non-domain environment
In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
below:
Sevrer1: 192.168.1.54
Server2: 192.168.1.53
Run
Enable-PSRemoting –Force on Server1. (Figure 20)
Figure 20.
Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
to
add the TrustedHosts entry:
Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
(Figure 21)
Figure 21.
Next, we can use
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
Figure 22.
After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
Figure 23.
From figure 24, we can see that the installation is completed.
Figure 24.
Then you can use
Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
The figure below shows the status of Windows Server Essentials.
Figure
25.
Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
Figure 26.
More information:
[Forum
FAQ] Introduce Windows Powershell Remoting
Windows Server Essentials Setup Cmdlets
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Command line enable of VNC/Remote Management?

I have a situation where I need to enable remove mgmt (VNC) on my Mac at work, so I can get to it over VPN at home, to access my Parallels, etc. I can ssh to the system, but can't figure out how to enable the Remote Desktop (and it's specific parameters) via the command line. I believe it would be a defaults write.
Can someone point me in the right direction? I just want to restrict VNC with a Password, then disable it when I'm done.
Thanks.

Hi
Difficult to see why you're hesitating to use the kickstart utility as that will do what you originally asked. Just because it does not specifically mention VNC does not mean VNC is not running or working.
VNC Server and Client is built into OSX since 10.5. If you enable Remote Management it will open ports 5900 and 3283 on that workstation. Port 5900 is the VNC Port and port 3283 is the special control port Apple add to the built in VNC/ARD Agent to allow their dedicated management VNC Server application - Apple Remote Desktop - to offer a lot more than simple control for remote clients. You don't have to buy ARD to do what you want.
Enabling Screen Sharing only opens port 5900. On a Mac all you need is the local admin's name and password of the client workstation you're trying to control. If you're trying to control a mac from a PC then you'd need a dedicated VNC Viewer installing on the PC. Something like RealVNC Viewer. To allow the PC to control the mac you would have to add a VNC password option which should not be the same as the local admin's password.
Tony

In System Preferences- Sharing- Remote Management the address doesn't reflect the computer name.

Hi,
I have a dual boot system with two seperate hard drives, Lion and Snow Leopard. One drive has a name of mac-pro2 for Lion and mac-pro2sl for Snow Leopard. Something happened when I rebooted from Snow Leopard to Lion that in System Preferences->Sharing->Remote Management that the computer name had changed to the Snow Leopard computer name it has a address and name of mac-pro2sl. I have change the Computer Name: and it worked and was changed to mac-pro2 but Remote Management still has the address of mac-pro2sl and doesn't reflect the computer name. I can ssh into Lion with mac-pro2sl but I have a conflict with from other computers when I log in with a warning of "Remote Host Identification has Changed". How do you change the computer name for remote management and ssh?
I have changed the hostname and it reflects the change when you login, mac-pro2 for Lion. But when you ssh into Lion it requires mac-pro2sl not mac-pro2.
When I change the computer name it shows below that the name in "Remote Management: On" "computer using the address mac-pro2sl" is selected but then doesn't change but remains the same when the dialog closes. How do you change the address to reflect the computer name? Is there a command line utility?
Thanks for any help.

If this problem is due to DNS, look in your configuration. What is the number one DNS server address? Is it local, or is it on the Internet at large? Or post the Address here and folks can help you look it up.
192.168.yyy.zzz
10.xxx.yyy.zzz
172.xxx.yyy.zzz
are all strictly local.

ZCM Agent 11.3.x - Remote Management - Windows User Variable

I noticed this back during the initial deployment of 11.3.1, however have not had a chance to comeback to it. Now we are at 11.3.2 and the issue seems to still be.
On login we have a script that runs via a bundle it tracks user, date, time, computer login info to 2 locations, one on the local workstation to a hidden folder and 2 on the network.....
It looks like this in the log file
"pwolfe" , "192.168.x.x" , "LPTP-PWOLFE" , "Tue 02/03/2015" , "11:44:20.05"
What I have noticed is if someone uses ZRM (Zen Remote Management) to manage the workstation / shadow a user for help or any other such thing...the next logon on the box will look like this
"LPTP-PWOLFE$" , "192.168.x.x" , "LPTP-PWOLFE" , "Tue 02/03/2015" , "11:44:20.05"
Notice the user variable went from the username to the computer name with a dollar sign. I would say it could be the script, however see below it works fine with the old agent installed.
If you reboot the computer its fine, you can login and out time after time and it will display correctly. However if someone remote manages the computer it is broke until the next restart.
here is the script that runs:
for /f "Tokens=2 Delims=[]" %%i in ('ping -4 -n 1 "%computername%"') do set IP=%%i
Echo "%username%" , "%IP%" , "%ComputerName%" , "%date%" , "%Time%" >>"\\192.168.x.x\support\utilities\logfiles\IPaddr essLog.txt"
Echo "%username%" , "%IP%" , "%ComputerName%" , "%date%" , "%Time%" >>"C:\Utilities\IPaddressLog.txt"
This is being called as a launch item under a user run bundle, it is set to run as logged in user.
This is not happening on the older 11.2.4 separate Zone / server setup that is still in use for the majority of people. Just on the newer 11.3.x environment.
If I remove the 11.3.x agent and install the 11.2.4 agent and point it to the old environment / server it works fine.
Any ideas?
Thanks,
Patrick

Originally Posted by CRAIGDWILSON
What happens if you create a Shortcut to this bundle and run it manually after the desktop is up and active? (after a RC session that messes stuff up?)
What happens if you create a bundle that runs "cmd.exe" as logged on user and run it manually while this other bundle is having issues? (type "set" from the cmd session....)
Thanks Craig,
I finally got some time to look at this again.
It appears on the first logon to a computer it runs correctly, if a Remote Management session takes place and once logged off and a log in is initiated you get the incorrect information. If you run the application from the Zen App Window it displays correctly. If you reboot the computer it works as expected for the first logon and then stops working if a remote session is initiated.
3 Straight logons, the 4th entry is when I ran it manually from the zen app window:
"pwolfe" , "192.168.30.75 " , "TDLARM280-50125" , "Tue 03/03/2015" , "14:53:33.77"
"TDLARM280-50125$" , "192.168.30.75 " , "TDLARM280-50125" , "Tue 03/03/2015" , "14:54:51.09"
"TDLARM280-50125$" , "192.168.30.75 " , "TDLARM280-50125" , "Tue 03/03/2015" , "14:57:24.29"
"pwolfe" , "192.168.30.75 " , "TDLARM280-50125" , "Tue 03/03/2015" , "14:58:22.51"
Here is the "Set" CMD
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\pwolfe\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=TDLARM280-50125
ComSpec=C:\Windows\system32\cmd.exe
DEFLOGDIR=C:\ProgramData\McAfee\DesktopProtection
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\pwolfe
LOCALAPPDATA=C:\Users\pwolfe\AppData\Local
LOGONSERVER=\\TDLARM280-50125
NUMBER_OF_PROCESSORS=4
NWLANGUAGE=ENGLISH
NWUSERNAME=pwolfe
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\Progra m Files (x86)\Intel\iCLS Clien
t\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows
\System32\Wbem;C:\Windows\System32\WindowsPowerShe ll\v1.0\;C:\Program Files\Inte
l\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Mana
gement Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management En
gine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Comp
onents\IPT;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Progra
m Files (x86)\Novell\ZENworks\bin;C:\Program Files (x86)\QuickTime\QTSystem\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WS F;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=3a09
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell \v1.0\Modules\
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\pwolfe\AppData\Local\Temp
TMP=C:\Users\pwolfe\AppData\Local\Temp
USERDOMAIN=TDLARM280-50125
USERNAME=pwolfe
USERPROFILE=C:\Users\pwolfe
VSEDEFLOGDIR=C:\ProgramData\McAfee\DesktopProtecti on
windir=C:\Windows
WINDOWS_LOGIN=0
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpac kage\csilogfile.log
ZENWORKS_HOME=C:\Program Files (x86)\Novell\ZENworks

Sharing - Remote Management - Allow Access = Broken

After upgrading to Mountain Lion, I was unable to connect to my new Mountain Lion remote desktops.
The upshot is that the Sharing -> Remote Management -> Allow Access settings are not AD/LDAP aware and it only works with local users now.
I had to turn off Remote Management and use Screen Sharing, where Allow Access is fully aware of local and non-local accounts.
Remote Managment -> Allow Access:
Screen Sharing -> Allow Access:
Your other option is to "Allow All Users" but I didn't want to do that.

I use the Vine Server for reduced color support. In my case it is my Mom's iMac 300 miles away and she has a slow DSL connection.
My experience with Mac OS X VNC server and client are that they work together very well, however, they do not play as nice with 3rd party clients and servers.
Since you are using Windows and by definition a 3rd party client RealVNC, I would suggest you install Vine Server. You can even configure it so it listens on port 5901 so it does not conflict with the Mac OS X VNC server.
<http://www.macupdate.com/info.php/id/11283/vine-server-%26-viewer>

Port based LB and Local Director

My customer would like to know whether the Local Director supports Load Balancing using the source port information. If this is possible any document on the configuration wouldbe highly appreciated.
Regards,
Mahesh

http://www.cisco.com/en/US/products/sw/iworksw/ps2769/products_maintenance_guide_chapter09186a008007d9fa.html#xtocid225795
as per this document i think the loadbalancing based on source port information cannot be done.
''The MNLB Services Manager makes the load-balancing decisions based on application availability, server capacity, and load distribution algorithms such as round robin or least connections, or the Dynamic Feedback Protocol (DFP).''

DNS, WINS, CompMgmt.msc Remote Management 2003 -- 2008-R2

My client has 3 WINS Servers which are (generally) replicating (push/pull partners all around).
In the MMC for WINS (and other services/consoles, CompMgmt and DNS specifically) we can add and connect from the 2008-R2 to the 2003 WINS (etc.) Servers.
From the 2003 to the 2008-R2 the connection fails with "Access denied".
The AD Users and Computers has no such issue.
I initially presumed that it must be either a port filter or some (perhaps obscure) registry/GPO security setting.
FYI: All of this is through an RDP session.
Any ideas on how to check and troubleshoot this?
HerbM

We have the local firewall turned off and all indications are that the switch/router firewalls are not blocking any of this. (These are all within one organization and and the checks that I have made have shown everything to be open.)
What specifically would need to be open for such remote management? Feel free to send me to some web resource etc. but so far I haven't found anything that would give me a definitive checklist.
I am pretty good with firewalls and such, good enough to be fairly certain that this is an open network, but also good enough to know that SOMETHING could be filtered that I am unaware of.
And it does actually say, "Access" denied.
-- HerbM

5508 remote management

We have several 5508 controllers, most can be remotely managed from most offices, which is useful for receptionists to access to create guest accounts. However we have one controller that can only be managed locally. Is there a security access list that could be preventing remote access?
If you try to access the web interface you just get the Internet Explorer cannot display this page message

Make sure ACL are configured correctly and its reachable from the local site and if you are able to locally configure it then only thing blocking is the ACL you can try if you can reach the port using any scanning tools also.

Using old version CS3. Can't "see" both Local and Remote files. Only Local.

Used to see both Local and Remote files. Worked in Local and then "Put" to the Remote when ready. Only see Local now. Work in Local is saved automatically to the server. Need to go back to the work in Local and Put to Remote. What happened? How do we fix it? Thanks!

Could you post a screen shot of what you're seeing when you go to...
Site > Manage Sites > Click the site you're working on > Edit
There should be two tabs in the upper left corner of the dialogue box that comes up, Basic and Advanced. Basic walks you through set-up with a bunch of questions and Advanced allows you to just enter the info into the correct fields. If the Advanced tab is open, it should be under the Remote heading where you set your FTP info.

Local Director Remote Management

Similar Messages

Maybe you are looking for