Windows 10: Using the "log on to" option in active directory requires adding the client?

I am using this feature to limit the a user so it can connect to a list of hosts, I'd like to define it in the AD to keep it centralized if possible.

After some trouble i found out this post here that explains that unless you add both the client and the server in the list it won't work.


Are there any workarounds for this? I am having trouble because this precise user is connecting from his computer that is not joined into our domain and I can't list all the hosts he will be using to connect from.

:)

 

Activation options for Win10 with instant clones

We have a secure (no internet access) lab environment setup to test and validate a VMWare VDI deployment of Win10 clients.

Our issue is activation of the Win10 clients as they require re-activation every time we logoff and back on because we are using instant clones.

Does anyone have any suggestions on the best way to resolve this? Here are the options we are considering and issues as we understand them:

• Setup a KMS server
  • Requires a Volume license, which is doable
  • Documentation says we must have a minimum of 25 hosts, we don' have that in our lab
• Use our MSDN account
  • No support for Win10 KMS license
  • No support for MKS activation
• Manually activate each time
  • Gonna spend a lot of time on the phone
  • Win10 has no grace period so machines are crippled w/o activation

Anyone have a thought or suggestions? I'm hoping I missed something.

Thanks

 

RealTimeLog.cvs Logs in Multiple Directories

Can you force the path setting for the RealTempLog.csv file?
Below are several scenarios of the RTL file starting or appending in two other directories than the RT directory.

The improvement: Force the RTS file to start in only one directory and append the file as the RT program starts/stops/starts, at Task Scheduling (startup or login), or any tests using the RT program.

My reason is I am using Excel PowerPivot and have set up pivot tables and charts that when ‘refreshed’ by PowerPivot, updates the tables and charts from the RTL file. Having the files start, stop, appends at various directories makes is a pain to ‘refresh’. There are ways to work around the problems, which maintains the link to a single file. Mainly; copying the file to the linked directory. However there is no continuous logging, which make me copy and paste from each log to the linked file. If all three RTL files are involved, it is a pain.

Anyhow, it would be very beneficial to force only one directory for logging the RTL file.

Below is some scenarios that represent the issue, as well as the RealTemp.ini information. Attached is more information in a zipped PDF file.

BTW, the program is awesome as it stands and thanks for the work you all have done to make it so.

Regards,
Dale

Dale Hamilton
L: dalehamilton@embarqmail.com

Here are the different scenarios regarding the directories, running ReatTemp (RT):
1. When starting RealTemp (RT) from the Task Scheduler at user login
a. RealTempLog.csv starts up in the Windows/SysWOW64 directory
b. Stopping RT, stops the log file in the Windows/SysWOW64 directory
c. Re-starting RT, starts a new RealTempLog.csv file in the RT directory
2. Stopping and starting RT after user login
a. Starts RealTempLog.csv file in the RT directory
b. Appends the log file with each start
3. Logging off while RT is still logging in the RT directory and then logging back on
a. RealTempLog starts logging in the Windows/SysWOW64 directory
b. The log file is appended at login time
c. The RealTempLog file in the RT directory stops logging at log-off time
4. Starting the XS Bench test
a. RTL continues to log in the directory that was logging at the time of starting XS Bench test
5. Starting the Sensor Test using Prime95 with the logging and log file at Windows/SysWOW64 directory
a. The RTL file closes in the Windows/SysWOW64 directory
b. The RTL file starts logging in the RT directory
c. The logging appends the RTL file
6. Starting the Sensor Test using Prime95 with the logging and log file at the RT directory
a. Closes the RTL file in the RT directory
b. Starts or appends the RTL file in the Prime95 directory
7. Starting the Sensor Test using Prime95 with the logging and log file at the Prime95 directory
a. Appends the RTL file at the Prime95 directory

RealTemp.ini Information:

[RealTemp]
;
;RealTemp 3.60
;September 30, 2010
;
;For further information and updates visit either of these sites:
;TechPowerUp
;Real Temp - New temp program for Intel Core processors
;
;Remove the semi-colon at the start of each line to try these options.
DegreeSymbolString=" ºC"
;
;How often the log file gets saved to the hard drive.
;Default is 60 seconds. Range is [1..86400] seconds.
HDWrite=1
;
;For Core 2 CPUs, use MSRMulti=1 to read the multiplier the traditional way.
;The default now is to use the same method that i7 Turbo uses for all processors.
;MSRMulti=1
;
;To read each CPU in a Skulltrail system use one of these.
;Skull=1
;Skull=2
;
;To use a calibratition formula similar to the original formula that has no affect
;on your reported temperatures between 70C and 100C use this. The original formula
;closely approximates what I found during testing.
;OldFormula=1
;
;Use the RealTemp Settings window to make all other adjustments.
;
WindowXY=562963771
IconTextColor0=0x80FFFF
IconTextColor1=0x80FF80
IconTextColor2=0xFFFF80
IconTextColor3=0xFF80FF
TjMax0=100
TjMax1=100
TjMax2=100
TjMax3=100
Idle0=0.0
Idle1=0.0
Idle2=3.0
Idle3=1.0
IconShow=0
LogFile=1
LogInterval=5
StartMinimized=0
TaskBar=1
FontNumber=
OnTop=0
TrayInfo=0
InfoWindow=
MiniMode=0
MinimizeOnClose=0
Spec=Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
RivaFile=C:\Program Files (x86)\RivaTuner v2.24 MSI Master Overclocking Arena 2009 edition\RivaTuner.exe
Alarm=0
Alarm1=100
Alarm2=100
CSV=1
AlarmFile=
VIDInfo=0
ClockMod=2
GUIColor=0xF4F3EE
GUIMiniColor=0xF4F3EE
GUIText=0x408000
GUIMiniText=0x000000
GUINormHead=0x000000
GUIMiniHead=0x000000
NormHeading=1
MiniHeading=0
TMLoad=0
CustomGUI=0
CustomGUIMini=0
CPUID=0x6FB
Quality=3
ThreeDigit=0
GPU=0
Fahrenheit=0
IconTextColor4=0x8080FF
AnchorXY=560407865
lfHeight=-16
lfWidth=0
lfWeight=400
lfItalic=0
lfCharSet=0
lfPitchAndFamily=18
lfFaceName=Times New Roman

 

Problem adding printer due to Active Directory Domain Services

Hi,

The Active Directory Domain Services is currently unavailable occurs when a new printer gets installed and the system is looking for the printer's driver. You can try the following steps below on how to add the printer nd see if it will resolve the issue:

• On the search bar, type troubleshooting and press Enter.
• On the left pane of the Control Panel window, click
  View all to view the list of apps.
• Look for the Printer from the list then right-click on it.
• Select Run as administrator.
• After doing so, try adding your printer again.

Don't hesitate to get back to us if you need further assistance.