Resolution of charts

Hi All,
On executing a WAD report, the graph does not have appropriate display. It is blurred and straight lines appear as several dots.
Are there any settings in WAD to improve the resolution of charts?? If yes, then where can I find these settings in WAD BI7.0?
Thanks,
Prerna

Hi,
select your chart--edit chart-go to step 4 element properties-there you can give the differen t types of properties like background, plot area, subtitle , legeng, other wise check in chart designer...
Regards
Harikrishna N

Similar Messages

Pie Charts causing Design mode to give warning and not preview the app

I am using the final release. I have pie charts in my app. I
also have column charts. Both are fed data the same way. Both work
as expected when i build the app, and there are zero errors in the
app. however, i was experiencing an issue in flexbuilder where in
design mode, a vague warning was issued and the preview could not
be displayed (blank except for very gernal 'outlines' of the layout
and controls)
I narrowed the problem down to the pie charts. Is anybody
experiencing this problem? The application worked as expected, and
previewed as expected in Design mode when previewd/built in Beta
3.

Hi masavran,
For this issue, it's related to the render environment (browser/application). On Reporting Services side, we don't have any properties to change the resolution for chart to make it smoothly. We suggest you post this thread on Visual Studio forum
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=visualstudiogeneral&filter=alltypes&sort=lastpostdesc
Or the forum of corresponding browser.
Best Regards,
Simon Hou

Quality of charts?

Is it me, or has the image quality of 3D charts in Pages (I must check out Keynote) taken a step backward with the latest update?
It's not something that I use a lot, but I remember being impressed only a couple of weeks ago when I did have a play around making some charts, just to see what the capabilities were.
Now the text, in particular, is very blurred. I'm just not getting the same wow-factor I had before. Am I just jaded?

Hi masavran,
For this issue, it's related to the render environment (browser/application). On Reporting Services side, we don't have any properties to change the resolution for chart to make it smoothly. We suggest you post this thread on Visual Studio forum
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=visualstudiogeneral&filter=alltypes&sort=lastpostdesc
Or the forum of corresponding browser.
Best Regards,
Simon Hou

Increase dpi of a image (Chart , process )

Hi All,
    I am getting the generated image of Charts , processes etc from Java(JFree Charts) to Flex.
But my requirement is to increase dpi of those charts in flex.
How to do that ...is there any solution for that??
thanks in Advance..

Hi All ,
    I am getting the generated image of Charts , processes etc from Java(JFree Charts) to Flex.
But my requirement is to increase dpi of those charts in flex or   Increase resolution of charts and process diagrams..
My code is like ::
private var image:Image;
image = new Image();
image.source = "Some url .. which generates chart in Java" ;
At this point .. after getting image in Flex .. i want to increase resolution of that image in AS3 .. i Heard about JPGEncoder
How to do that ...is there any solution for that??
Thanks..

Primary DNS resolution slow if PDC role DC is down

Hello,
In my environment I'm running purely Windows Server 2012 in a two site environment. I run a single domain infrastructure with my main site that has 2 domain controllers (one has all FSMO roles), and a second site which has a single domain controller.
I've been looking all over the forums for a related topic, but haven't read something anything that fits my scenario. Basically what happens is, if the DC that has FSMO roles (specifically PDC) goes offline, or if I were to turn the DNS service
off, all devices would take forever for DNS resolution. Another scenario (which is essentially the same) is if the VPN tunnel between the two sites goes down, all clients at site 2 would take awhile for DNS resolution. If those clients launch their
browser any website they go to takes 5-10 seconds to load. They could reboot their PC, and do ipconfig /flushdns, and even though those clients DNS settings point to the DC at site 2 as primary DNS, it takes awhile. As soon as the PDC server is
restored everything is back to normal. Quite frequently the VPN tunnel will go down leaving very slow responses at site 2. Oddly enough is, if the tunnel were to go down, and I logged into the DC at site 2, if I were to ping various domains the
response would take 5 or so seconds. Is this normal to occur? If not, how could I possibly remedy this? My assumption is that, if the primary DNS were to go down, or in this case the PDC server goes down, one of the secondary servers would
kick in. I appreciate any light you can shed on this issue.
Ken

I agree with Meinolf. It's not always the DNS or PDC or whatever DC is in question's, fault. A lot of it is due to the client side resolver algorithm. Here's more specifics on how the whole process works - and note that this applies to all operating systems,
Windows, Linux, Unix, BEOS..... because they all follow the RFCs defining how client side resolvers work.
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
http://tools.ietf.org/html/rfc882
=============
To add on how the client resolver picks a nameserver, below is a link to a discussion that points out the following - and please note, the operative point in the first bullet point indicates "equivalent," meaning that all DNS servers you enter into a NIC,
must all reference the same exact data, so you can't mix nameserver with different data and expect the client to try all of them.
•by RFC, all nameservers in a zone's delegation are equivalent
•they are indistinguishable to the client
•clients are allowed to choose the NS to query with whichever policy they wish
•if any picked server fails to respond (e.g. "ns3"), then the next server is picked among the remaining set (e.g. ns1 and ns2) according to the policy
•often clients use sophisticated policies that "score" servers and pick more often the ones that replied faster
•as a by-product, in practice this policy makes caches favor "nearest" servers
That was quoted from:
When is a secondary nameserver hit?
http://serverfault.com/questions/130608/when-is-a-secondary-nameserver-hit
===============
So you have to check when the first DNS goes down, not all directory enabled apps can handle it. opened.
Another issue is the client has bounded to the logon server during the DC Locator process. That's difficult to mess with other than restarting the machine...
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

2K8 - Best practice for setting the DNS server list on a DC/DNS server for an interface

We have been referencing the article
"DNS: DNS servers on <adapter name> should include their own IP addresses on their interface lists of DNS servers"
http://technet.microsoft.com/en-us/library/dd378900%28WS.10%29.aspx but there are some parts that are a bit confusing. In particular is this statement
"The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain
controller and it points only to itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller.
The loopback address should be configured only as a secondary or tertiary DNS server on a domain controller.”
The paragraph switches from using the term "its own IP address" to "loopback" address. This is confusing becasuse technically they are not the same. Loppback addresses are 127.0.0.1 through 127.255.255.255. The resolution section then
goes on and adds the "loopback address" 127.0.0.1 to the list of DNS servers for each interface.
In the past we always setup DCs to use their own IP address as the primary DNS server, not 127.0.0.1. Based on my experience and reading the article I am under the impression we could use the following setup.
Primary DNS: Locally assigned IP of the DC (i.e. 192.168.1.5)
Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
Tertiary DNS: 127.0.0.1
I guess the secondary and tertiary addresses could be swapped based on the article. Is there a document that provides clearer guidance on how to setup the DNS server list properly on Windows 2008 R2 DC/DNS servers? I have seen some other discussions
that talk about the pros and cons of using another DC/DNS as the Primary. MS should have clear guidance on this somewhere.

Actually, my suggestion, which seems to be the mostly agreed method, is:
Primary DNS: Locally assigned IP of the DC (i.e. 192.168.1.5)
Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
Tertiary DNS: empty
The tertiary more than likely won't be hit, (besides it being superfluous and the list will reset back to the first one) due to the client side resolver algorithm time out process, as I mentioned earlier. Here's a full explanation on how
it works and why:
This article discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB).
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders)
Client side resolution process chart
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-
logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS
Client side resolver service
http://technet.microsoft.com/en-us/library/cc779517.aspx
The DNS Client Service Does Not Revert to Using the First Server in the List in Windows XP
http://support.microsoft.com/kb/320760
Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
I agree with this proposed solution as well:
Primary DNS: Locally assigned IP of the DC (i.e. 192.168.1.5)
Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
Tertiary DNS: empty
One thing to note, in this configuration the Best Practice Analyzer will throw the error:
The network adapter Local Area Connection 2 does not list the loopback IP address as a DNS server, or it is configured as the first entry.
Even if you add the loopback address as a Tertiary DNS address the error will still appear. The only way I've seen this error eliminated is to add the loopback address as the second entry in DNS, so:
Primary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
Secondary DNS: 127.0.0.1
Tertiary DNS: empty
I'm not comfortable not having the local DC/DNS address listed so I'm going with the solution Ace offers.
Opinion?

How to setup IP address for DC&ADC

Hello ,
I have DC server and ADC server I need to configure IP address for both server
correctly ,kindly tell me how do that.
because I have problem : on DC server computer container is empty all computer in my network
appear in ADC however if you search for any computer in DC I can find it
Note: If you have created any user in the server immediately user appear on the other server
thanks

I see, you are worried about what would happen with your Exchange server if one of your DCs go down.
That's not an easy question to answer. It's a very complex question because there are multiple components at play.
First, let's discuss the client side resolver. Each operating system has one no matter if it's a DC, server, workstation, Apple, Unix, Linux, Android, etc. The way they work is based on the industry standard RFCs that explain how they work.
The client side resolver will only look at the second DNS entry if the first entry returns a NULL response (no response) after a time out period. However, if the client side resolver already has the record cached (you can see the cache by running ipconfig
/displaydns) for the TTL of the record, and the DC goes down, well the client side resolver will not query again because it sees it already has it in cache.
Exchange will automatically look for another LDAP, Config and GC if the one it's using goes down. However, Outlook isn't so forgiving. It locks on to a GC and a DSProxy for the Exchange server. If the GC goes down, you have to restart Outlook. That's going
to be difficult if you have lots of users.
And if Exchange is on a DC, that doesn't work that way because it *locks* on to the DC/GC it's installed on. I hope your Exchange server is not on a DC.
Here's more specifics on how the whole process works - and note that this applies to all operating systems, Windows, Linux, Unix, BEOS..... because they all follow the RFCs defining how client side resolvers work.
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
http://tools.ietf.org/html/rfc882
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Backup DNS Records

Afternoon,
Is there a way to create a back-up A record in order to provide redundancy?
I'm currently in the middle of setting up a DR site and looking to find a way to have a set of DNS record pointing at existing servers host name but with different IP addresses so in the event that we require to bring a replicated server up at the DR site
the DNS record would automatic switch over after the TTL has expired on the primary link.
our DNS service runs on a windows server 2012 environment in a cluster of 3 servers for redundancy.
Thanks

To answer/address the question about the same records with different IPs, unfortunately it doesn't work that way with AD. The IPs registered are absolute for the service locations, and they must be consistent across the organization for AD DC to DC communications
including replication, and client to DC communications. If you attempt to alter them, it will cause numerous errors and additional headaches that I'm sure you do not want to deal with.
Just setup two DCs at the DR, do not make them GCs. Just make them GCs in case a down issue occurs. Depending if you have 3 or more sites, this may also require to make individual site links for each site and disable BASL. The reasons are long winded,
but it's technically how AD works. You can design around it, but you can't mess with DNS. And keep in mind, just because they are up, services and client apps may not be so forgiving to "see" the DR servers until they've been restarted.
So there's more to this than it appears.
You can read up in this stuff in the following link:
AD Site Design, DNS & the DC Locator Process, and Auto Site Link Bridging, or Bridge All Site Links (BASL)
http://blogs.msmvps.com/acefekay/2013/02/24/ad-site-design-and-auto-site-link-bridging-or-bridge-all-site-links-basl/
The blogs below discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://blogs.msmvps.com/acefekay/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm/
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

DNS resolving to external IP when ping.

Hi expert folks...have a question....when pinging to some of the client with in the LAN it resolve to external public IP instead of private IP ...i had checked and confirmed the client that that clients configured to DNS server IP with in the LAN.No external
DNS been configured...this doesn't not occur all the time with all clients...its happened some time with some clients...after few minutes when we re-ping or after refresh it is back to normal private IP.....Could please advice what could be the possibility
of this..?

Hi...Thanks for your guidance ...I had verified the configuration you mentioned on your post... DNS search suffix order was fine so i haven't made any changes on that ...also TTL time remains as default...i found that some clients have external
DNS on their DNS configuration list ...I had removed those........still i wonder even if external DNS configured it should be only in action ,when primary and secondary internal DNS cannot resolve .Also another interesting this i noticed ,when the address
resolved to external DNS the TTL is 65 and when it resolve to internally TTL 128 for all clients.I guess it jumping to external DNS bypassing internal DNS servers.So far i haven't experience same issue again that's why I cannot provide the outcome of
nslookup...appreciate your help and guidance.
The root cause was the external DNS servers on your clients. The DNS client side resolver service algorithm, looks at the first entry, and ONLY if it does not answer, which results in a NULL or NACK response, will it go to the second entry. If it does answer,
even if the answer is an "I don't know," the client will take that as an answer and look no further. This algorithm, in case you're wondering, which many do, is not just the way Microsoft operating systems work. It's based on the IETF RFC industry standards
that all manufacturers must adhere to.
The proper way to configure all machines, especially in an AD environment, is to only use your internal DNS servers on every machine, nothing else, including the router as a DNS address (you would be surprised how many do use that because the ISP told them
it's ok), and in your DNS server properties, you can optionally configure a forwarder to your ISPs. That's the only place any external DNS servers can exist internally, in a Forwarder or Stub.
More on the resolver service:
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Recursive and authoritative DNS - DDOS attack

We are using Windows Server DNS as our external DNS server which is available from internet and used to resolve our domain names. It is placed in DMZ. It is configured as recursive and authoritative. In internal company network we have
4 Windows DNS servers which have forwarders configured for this DNS server in DMZ. If some attacker from the internet will try to use our DNS server placed in DMZ and available from internet for a lot of recursive queries it could result in denial of service.
What is the best practice to avoid such attack?

Actually, there's a rather complex algorithm that's used that's similar to, if not the same as, what the client side resolver on any machine (Windows and non-Windows) uses. It's an industry standard based on RFC definitions.
More specifics in the following links, if you want to read up on it. And to one's surprise, it doesn't exactly work as one would like it to. The idea is to keep both up and the other one as a backup in case you fully lose the first one.
DNS Client side Resolver Service and DNS Forwarders Query Algorithm
http://blogs.msmvps.com/acefekay/2014/03/29/dns-client-side-resolver-service-and-dns-forwarders-query-algorithm/
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
http://blogs.msmvps.com/acefekay/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm/
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
http://tools.ietf.org/html/rfc882
==
To add on how the client resolver picks a nameserver, below is a link to a discussion that points out the following - and please note, the operative point in the first bullet point indicates "equivalent," meaning that all DNS servers you enter into
a NIC, must all reference the same exact data, so you can't mix nameserver with different data and expect the client to try all of them.
•by RFC, all nameservers in a zone's delegation are equivalent
•they are indistinguishable to the client
•clients are allowed to choose the NS to query with whichever policy they wish
•if any picked server fails to respond (e.g. "ns3"), then the next server is picked among the remaining set (e.g. ns1 and ns2) according to the policy
•often clients use sophisticated policies that "score" servers and pick more often the ones that replied faster
•as a by-product, in practice this policy makes caches favor "nearest" servers
Above list was quoted from:
When is a secondary nameserver hit?
http://serverfault.com/questions/130608/when-is-a-secondary-nameserver-hit
I hope that helps to understand it better.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Failover to remote DC after disaster

I suspect this question has already been answered and apologize in advance for repetition. Here is my current setup:
Site A: Windows Server 2008 R2 running AD/DNS/DHCP. Main domain controller resides here.
Site B: Windows Server 2008 R2 running AD/DNS/DHCP. Second domain controller at remote office.
The two sites are interconnected by a private, leased line running at around 10Mbps. I have configured my sites, subnets, etc. and the two DCs are properly replicating.
What I am searching for is a document that will describe the actual procedures that I need to implement at Site B in the event Site A burns to the ground. I am hunting for the actual procedure for failing-over to the DC at Site B in the event of complete
disaster.
Thanks

Maybe my blog will help a little with understanding how replication works across WANs, configuring site links, BASL (meshed sites vs non-meshed), the DC location process, GC placement (might want to make all DCs a GC), and much more.
AD Site Design, DNS & the DC Locator Process, and Auto Site Link Bridging, or Bridge All Site Links (BASL)
http://blogs.msmvps.com/acefekay/2013/02/24/ad-site-design-and-auto-site-link-bridging-or-bridge-all-site-links-basl/
You'll also need to understand how the client side resolver works, because that's a major component in the big picture because the DNS settings on the client and how the resolver service algorithm works. The client doesn't bounce back and forth between the
DNS entries in the NIC. It follows a certain algorithm no matter if it's a DC, server, workstation, Apple, Unix, Linux, Android, etc. The way they work is based on the industry standard RFCs that explain how they work.
DNS Client side Resolver Service and DNS Forwarders Query Algorithm
http://blogs.msmvps.com/acefekay/2014/03/29/dns-client-side-resolver-service-and-dns-forwarders-query-algorithm/
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
http://tools.ietf.org/html/rfc882
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Copy-paste of a chart or table in new iWork creates a low resolution raster rather than a vector

In iWork '09 I regularly copied charts, tables, etc. from iWork applications to other applications. They were in vector format. For instance, I have made a chart in Numbers, copied it, and pasted in Preview. This resulted in a vector which I saved to PDF, everything in less than 5 seconds.
It seems that in the new iWork this is not possible anymore, because the result is a low-resolution raster, which totally broke my workflows.
Is this an "enhacement" of the new iWork or I am missing something?

Hi Badunit,
A possible explanation for our discrepency:
If I copy an entire page from a vector pdf using the thumnails bar in preview and paste that page into keynote, the image is a raster.
If I select a portion of that page with the preview selection tool, copy, and paste into keynote, the image is a vector.
This issue is especially damaging because I can't drag and drop pdf files I create into keynote. Major bugs have been introduced with regards to vector images, and I'm unable to identify a single rule characterizing this process. This is a disaster as I've relied on keynote as a longterm storage and organization tool for many vector images. Many of these images have now been corrupted in what I assume is an irreversible process.

Excel chart into InDesign - resolution problem

Hello, I am working on a Mac OS 10.8.3 and using InDesign CS6
I have to place a chart that was created in Excel into InDesign and I realize there is a resolution problem if we start to print.
Would you suggest I create the chart using an Adobe product? I am just trying to save time, but I'm afraid that may be the only answer.
I have a screen shot below of kind of what it looks like. I have about 25 of these.
Thank you.

I tried pasting the chart from Word into Excel and then I dragged that chart into Illustrator and then copied into InDesign. Probably used an extra step there, but..
I went to this site for help too; http://helpx.adobe.com/indesign/kb/import-excel-data-charts-graphs.html
The text comes in a little funny, but I redid the text boxes and I was able to get in and edit some of the elements.
Thank you!

Report resolution (96DPI or higher than 96 DPI) in regards to image quality

We have discovered that the default rendering mode for reports in WebI is 96 DPI, even though the SDK seems to allow more flexibility than that, so we are wondering if there is some hidden option to cause WebI to render content at a higher DPI.
The specific problem we are having is in regards to some images that render very poorly at 96 DPI in our reports. We can render them at a higher DPI (say 300 DPI for better print quality) and then allow them to be scaled down using the "Stretch" option, but the quality is not nearly as good as our imaging software, and the solution does not work in HTML mode. So that's not an option.
To be honest, I'm surprised about the way things work in this regard, because we should be able to produce high quality images in our reports. 96 DPI is never used for final print quality work. At least InfoView has an option for CrystalReports to render at 120 DPI, but I'm not sure if that only effects the display or not, and if it automatically adjusts offsets that were calculated at 96 DPI when the report was designed.
If we could somehow determine the display mode in a function (e.g., print versus display, or get the DPI, or PDF/HTML/JRP, or something), then we might be able to use a different image (each rendered at a different DPI) depending on the mode. That would be an odd workaround, but if there's no way to change the resolution, this would be great also.
Any suggestions on either front? We need these images to display with at least a "normal" print quality resolution.

Please refer to SAP Knowledge Base Article 1307814 - File size is disproportionately large when Web Intelligence 3.1 report with charts is saved to PDF format .
Pasting the resolution details below:
For WebIntelligence version XIR2
Install BOXIR2 Service Pack 4 FP 4.10 : in this release, developers have given the option to edit the DPI setting.
To solve this problem, change the resolution to 96 DPI in the webiviewer.properties file at the following location :
<ApplicationServer-Webapps>/businessobjects/enterprise115/desktoplaunch/WEB_INF/classes/ webiviewer.properties
For BOXI3.1, the DPI setting remains as default 300.
To solve the problem edit the DPI value in this xml file under the pdf section where the comment says you can edit in the path :
<installed directory>\win32_x86\config\bobjserver\caching_media_profiles.xml
2. Restart the servers
Note : Take necessary back up of the files before doing any changes. Also any new patches if applied, you might be required to re-do the changes to the respective files. Please edit the files carefully ONLY under the sections which says you can edit the DPI Values.

Outlook 2013 with SSRS charts in MHTML displays wrong image in email

Hi,
I've posted this question already to the SQL Server group and the SQL Team confirms this is potentially an issue with Outlook 2013 and image cache changes between 2010 and 2013. Please see the more detailed post here for more information: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/e34516c5-53cd-4792-bc6d-4cb6e41e63cf/ssrs-2012-with-mthml-subscriptions-graphs-and-outlook-cache-issues?forum=sqlreportingservices
In short, when changing between emails that display charts from SSRS distributed via MHTML, Outlook 2013 will display the wrong graph from its image cache. This issue does NOT happen when opening the email in a browser by using the "View in Browser"
option from the Information ribbon in the email.
The issue began after upgrading from Outlook 2010 to 2013 so it would appear that the image cache algorithm has changed. We need a resolution to stop this from happening that does not include turning off cached exchange mode. I've tried changes
in the Trust center by turning off the viewers but that doesn't fix anything.
We are using Office 365 and Outlook 2013 x64 SP1.
Has anyone else experienced this or found a workaround for the issue? This is what it looks like when clicking between emails and then opening in the browser.
Thanks,
Kevin

Outlook uses Word as an email editor. That's why you may see the difference between the browser and Outlook inspectors. See the following series of articles for more information:
Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 1 of 2)
Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007 (Part 2 of 2)

Resolution of charts

Similar Messages

Maybe you are looking for